Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 4 Oct 2017 17:52:00 +0000 (UTC)
From: "Antonenko Alexander (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13107008.1507139338000.272193.1507139520420@Atlassian.JIRA>
In-Reply-To: <JIRA.13107008.1507139338000@Atlassian.JIRA>
References: <JIRA.13107008.1507139338000@Atlassian.JIRA> <JIRA.13107008.1507139338622@jira-lw-us.apache.org>
Subject: [jira] [Updated] (AMBARI-22134) UI Fixes for Maint Repo Version
 Display
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 Oct 2017 17:52:05 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-22134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonenko Alexander updated AMBARI-22134:
-----------------------------------------
    Status: Patch Available  (was: Open)

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