[
https://issues.apache.org/jira/browse/AMBARI-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169966#comment-15169966
]
Hudson commented on AMBARI-15158:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.2 #424 (See
[https://builds.apache.org/job/Ambari-branch-2.2/424/])
AMBARI-15158. Resource Manager fails to start: IOException: /ats/active
(stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c4c1b74bc75947e795a5ce3dd564bc0fa3f9243f])
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py
> Resource Manager fails to start: IOException: /ats/active does not exist
> ------------------------------------------------------------------------
>
> Key: AMBARI-15158
> URL: https://issues.apache.org/jira/browse/AMBARI-15158
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: Sebastian Toader
> Assignee: Sebastian Toader
> Priority: Critical
> Fix For: 2.2.1
>
> Attachments: AMBARI-15158.2.2.1-maint.v2.patch,
> AMBARI-15158.branch-2.2.v2.patch, AMBARI-15158.trunk.v2.patch,
> hdp-small-default.bp, yarn-yarn-resourcemanager-host-10-0-0-5.log
>
>
> Resource Manager fails to start when cluster is provisioned with blueprint
> for the first time. After RM restart it works so it could be a sync issue.
> Log and blueprint attached.
> Config recommendation strategy is ONLY_STACK_DEFAULTS_APPLY
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
