You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2016/02/11 00:50:18 UTC

[jira] [Commented] (AMBARI-14886) Express Upgrade - Versions - Current Version

    [ https://issues.apache.org/jira/browse/AMBARI-14886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141974#comment-15141974 ] 

Alejandro Fernandez commented on AMBARI-14886:
----------------------------------------------

[~mbsharp85], can you provide steps to reproduce with the exact source stack and destination stack.
Any database dumps you can attach or ambari-server.log?

> 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
>
> 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)