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

Hudson commented on AMBARI-18506:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5756 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5756/])
AMBARI-18506 Ambari should present message if stack upgrade path is not 
(atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=269494849cad6d0a56dddaf52316e1d84b08d49f])
* (edit) ambari-web/app/models/stack_version/repository_version.js
* (edit) 
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs
* (edit) 
ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js
* (edit) ambari-web/app/messages.js
* (add) ambari-web/test/mappers/repository_version_mapper_test.js
* (edit) ambari-web/app/assets/test/tests.js
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit) ambari-web/app/mappers/repository_version_mapper.js
* (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
* (edit) 
ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js
* (edit) 
ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* (edit) 
ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
* (edit) 
ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_box.hbs


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

Reply via email to