[
https://issues.apache.org/jira/browse/AMBARI-14350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054595#comment-15054595
]
Hudson commented on AMBARI-14350:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.2 #65 (See
[https://builds.apache.org/job/Ambari-branch-2.2/65/])
AMBARI-14350. AMS is broken after redeploy cluster (Aravindan Vijayan
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5e4f9573bc12143d9bd8594024ea4293f1ddbf8f])
*
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
*
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
*
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py
> AMS does not start up after cluster redeploy because of invalid ownership of
> its directories.
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-14350
> URL: https://issues.apache.org/jira/browse/AMBARI-14350
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14350.patch
>
>
> PROBLEM
> Steps:
> Deployed cluster via blueprints.
> Reset cluster (reset ambari-server, host cleanup).
> Deployed cluster via UI.
> Result: Ambari Metrics Service go down.
> BUG
> AMS scripts do not change the ownership of certain directories to AMS user if
> they exist already.
> FIX
> Adding an explicit chown to take ownership of the required directories
> (collector conf, collector checkpoint, HBase tmp, HBase conf, HBase root)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
