[
https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905940#comment-15905940
]
Hadoop QA commented on AMBARI-20401:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857416/AMBARI-20401.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 1 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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10977//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10977//console
This message is automatically generated.
> HOU wizard wrongly shows hosts with only client components at the start of
> 'Upgrade Hosts' group
> ------------------------------------------------------------------------------------------------
>
> Key: AMBARI-20401
> URL: https://issues.apache.org/jira/browse/AMBARI-20401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20401.patch
>
>
> # Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts
> with only masters, 2 hosts with only slaves, 1 host with only clients)
> # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that
> host named 'bugbash-cluster-2-2.openstacklocal' - third in the list has only
> client components)
> In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All
> Hosts' group, there is already an entry for 'Stop on
> bugbash-cluster-2-2.openstacklocal'
> Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal
> does not have any master/slave components it is already considered that
> components are stopped on this host and the entry shows up in wizard.
> Likewise From API, I checked that the Upgrade item appears as COMPLETED, even
> though earlier Upgrades items are still Pending.
> Thanks to [~shavi71] for finding this...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
