ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14886) Express Upgrade - Versions - Current Version
Date Thu, 11 Feb 2016 14:22:18 GMT

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

Matt Sharp commented on AMBARI-14886:
-------------------------------------

[~afernandez] I attached the ambari-server log and a couple screenshots showing the scenario.

Steps to reproduce:
1. Start with a clean HDP 2.2.4.12 installation (Ambari 2.2.0) 
2. Go through an express upgrade to HDP 2.3.4.0
3. Select finalize upgrade later
4. Check versions view, you will see the 2.2.4.12 still marked as "current"
5. Check the stacks view, you will see the component versions matching HDP 2.3.4.0 (compared
to release notes)

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

Mime
View raw message