You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/04/09 16:17:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16430790#comment-16430790 ]
Hudson commented on AMBARI-23505:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9017 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9017/])
AMBARI-23505 - Cluster version is not updated after stack upgrade (#928) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=aea0869c766050690e1c02037edbc5c4f6800700])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/UpdateDesiredRepositoryAction.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackManager.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerMock.java
> 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
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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)