[jira] [Updated] (AMBARI-23505) Cluster version is not updated after stack upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23505: Labels: pull-request-available (was: ) > Cluster version is not updated after stack upgrade > --- > > Key: AMBARI-23505 > URL: https://issues.apache.org/jira/browse/AMBARI-23505 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Yolanda M. Davis >Assignee: Jonathan Hurley >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > While testing a case where we upgrade, downgrade, then upgrade HDF stack, we > noticed that the cluster version value was not updated (expected to go from > HDF 3.1 to HDF 3.2). Ambari did complete the upgrade process without error, > and new components libraries were installed, however the newer service > advisors for the stack were not executing and expected new configurations did > not appear. Upon further investigation we saw that after upgrade the cluster > version had not been updated from HDF 3.1 to HDF 3.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23505) Cluster version is not updated after stack upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-23505: - Reporter: Yolanda M. Davis (was: Jonathan Hurley) > Cluster version is not updated after stack upgrade > --- > > Key: AMBARI-23505 > URL: https://issues.apache.org/jira/browse/AMBARI-23505 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Yolanda M. Davis >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.7.0 > > > While testing a case where we upgrade, downgrade, then upgrade HDF stack, we > noticed that the cluster version value was not updated (expected to go from > HDF 3.1 to HDF 3.2). Ambari did complete the upgrade process without error, > and new components libraries were installed, however the newer service > advisors for the stack were not executing and expected new configurations did > not appear. Upon further investigation we saw that after upgrade the cluster > version had not been updated from HDF 3.1 to HDF 3.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
