[jira] [Commented] (AMBARI-18506) Ambari should present message if stack upgrade path is not available

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-18506:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12831110/AMBARI-18506.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-web.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/8784//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8784//console

This message is automatically generated.

> Ambari should present message if stack upgrade path is not available
> --------------------------------------------------------------------
>
>                 Key: AMBARI-18506
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18506
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 2.4.2
>
>         Attachments: AMBARI-18506.patch
>
>
> After adding a new stack version to Ambari and selecting it to be installed on a specific cluster, the UI changes to the cluster versions page. If the upgrade path (aka the upgrade pack) is not available for the transition from the current stack version to the new stack version then the selected version is not seen on that next screen. This transition is silent leaving the user confused as to where the version went.
> For example: Adding HDP 2.5 to a cluster where the current stack is HDP 2.2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)