[
https://issues.apache.org/jira/browse/AMBARI-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290168#comment-15290168
]
Hadoop QA commented on AMBARI-16750:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804822/AMBARI-16750-trunk-orig.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/6888//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6888//console
This message is automatically generated.
> Activate HAWQSTANDBY fails on retry
> -----------------------------------
>
> Key: AMBARI-16750
> URL: https://issues.apache.org/jira/browse/AMBARI-16750
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.4.0, 2.4.1
> Reporter: Matt
> Assignee: Matt
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16750-trunk-orig.patch
>
>
> If wizard failed on the Activate Standby step, retrying the step would cause
> a failure, because the master hosts have been switched already in the
> configuration.
> Resolution: Before retrying the command, rewrite the configuration with
> current topology.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
