[
https://issues.apache.org/jira/browse/AMBARI-22134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191874#comment-16191874
]
Hudson commented on AMBARI-22134:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8206 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8206/])
AMBARI-22134. UI Fixes for Maint Repo Version Display (alexantonenko)
(aantonenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d86f76497e20b17c7ca381b3941d3fd0f82aeebf])
* (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
> UI Fixes for Maint Repo Version Display
> ---------------------------------------
>
> Key: AMBARI-22134
> URL: https://issues.apache.org/jira/browse/AMBARI-22134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.6.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22134.patch
>
>
> STR:
> Install 2.6.0.0 base of ZK + STORM.
> Register/Install/Upgrade a MAINT VDF to 2.6.0.3 that includes STORM + KAFKA
> Upgrade will be Storm only
> Register/Install/Upgrade another MAINT VDF to 2.6.3.0 that includes
> STORM+KAFKA
> Add Kafka service.
> The 2nd repo becomes OUT_OF_SYNC (that's ok)
> Reinstall and Upgrade (Kafka becomes upgraded)
> When reverting the (correct) last upgrade, orchestration would be ONLY for
> Kafka, since that was the last upgrade, but the dialog says that both Storm
> and Kafka will be reverted. This is incorrect, it should only show Kafka.
> This information is correct in the Upgrade History tab. You should be
> querying the upgrade endpoint for revert_upgrade_id to know what to show on
> the popup.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
