[
https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429502#comment-15429502
]
Hadoop QA commented on AMBARI-18220:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824709/AMBARI-18220.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8472//console
This message is automatically generated.
> Namenode start failed on moving namenode on a HA cluster
> ---------------------------------------------------------
>
> Key: AMBARI-18220
> URL: https://issues.apache.org/jira/browse/AMBARI-18220
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18220.patch
>
>
> *STR:*
> 1. Enable NameNode HA
> 2. Launch "move namendode" wizard
> *Actual Result:* On the page "Configure Component" at the step to start
> namenode, both namenodes are started. This leads to failure of the request
> intermittently
> *Expected Result:* Only one namenode "the one which is not being moved"
> should be started
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
