[
https://issues.apache.org/jira/browse/AMBARI-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167579#comment-15167579
]
Hudson commented on AMBARI-13002:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4388 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4388/])
AMBARI-13002. Turning on the Maintenance mode wouldn't let you install (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ed954bbe86575d8aa0730968c4642807fb87a6d5])
* ambari-web/app/controllers/main/admin/highAvailability_controller.js
* ambari-web/app/messages.js
> Turning on the Maintenance mode wouldn't let you install the additional
> components properly
> --------------------------------------------------------------------------------------------
>
> Key: AMBARI-13002
> URL: https://issues.apache.org/jira/browse/AMBARI-13002
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin, ambari-server
> Affects Versions: 2.0.2
> Environment: RHEL 6.x, HDP2.2.4.12
> Reporter: Basha Shaik
> Assignee: Antonenko Alexander
> Labels: patch
> Attachments: AMBARI-13002_22.patch, AMBARI-13002_trunk.patch
>
>
> Scenario:
> 1. Turn on the maintenance mode on HDFS service to suppress alerts
> 2. Add Name Node HA
> 3. During the adding addional name nodes and journal nodes, the amabri server
> supposed to stop the name node service but it wouldn't stop.
> 4. As a result there is a lock on the HDFS and nameNode initializeEdits steps
> fail
> Expected Result:
> Even when in maintenance mode, Amabri should be able to add services, start
> and stop the services as required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
