[
https://issues.apache.org/jira/browse/AMBARI-14886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145059#comment-15145059
]
Alejandro Fernandez commented on AMBARI-14886:
----------------------------------------------
Actually, that is expected behavior.
By clicking on "Finalize Later", the EU finishes and it is up to the user to
finalize save the new version as CURRENT by calling,
{code}
sudo su hdfs -c "hdfs dfsadmin -rollingUpgrade finalize"
ambari-server set-current --cluster-name=$CLUSTERNAME
--version-display-name=$VERSION_NAME
{code}
https://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.1/bk_upgrading_Ambari/content/_Set_Current_HDP_Version_mamiu.html
While not yet finalized, it is not recommended to add services, hosts, or
restart some services via Ambari.
> Express Upgrade - Versions - Current Version
> --------------------------------------------
>
> Key: AMBARI-14886
> URL: https://issues.apache.org/jira/browse/AMBARI-14886
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
> Affects Versions: 2.2.0
> Reporter: Matt Sharp
> Priority: Trivial
> Attachments: ambari-server.log, stacks_view.png, versions_view.png
>
>
> After completing an Express Upgrade with Ambari 2.2.0 the active version is
> not accurate when viewing the Versions page within Stacks and Versions.
> Ambari still flags the previous version as the active version when you do not
> finalize the upgrade right away. The Stacks page does show the correct
> active versions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
