ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-22134) UI Fixes for Maint Repo Version Display
Date Wed, 04 Oct 2017 18:22:00 GMT

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

Hadoop QA commented on AMBARI-22134:
------------------------------------

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

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

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

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

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

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12430//console

This message is automatically generated.

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

Mime
View raw message