[
https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429583#comment-15429583
]
Hudson commented on AMBARI-18220:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5562 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5562/])
AMBARI-18220. Namenode start failed on moving namenode on a HA cluster.
(jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5eb69463ed475072ab4a0a038e6f35d5b9b70fe2])
* (edit) ambari-web/app/controllers/main/service/reassign/step4_controller.js
* (edit)
ambari-web/test/controllers/main/service/reassign/step4_controller_test.js
* (edit) ambari-web/app/views/main/service/reassign/step5_view.js
> 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
> Labels: 240RMApproved
> 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)
