[
https://issues.apache.org/jira/browse/AMBARI-13099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804853#comment-14804853
]
Hudson commented on AMBARI-13099:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3460 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3460/])
AMBARI-13099. Config changes w/ blueprint provisioning are not picked up
(Oliver Szabo via smohanty) (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d40bf10b8fc2be9046e278f4bd2685fc62f06513)
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
> Host group level config changes are not picked up with Blueprint provisioning
> -----------------------------------------------------------------------------
>
> Key: AMBARI-13099
> URL: https://issues.apache.org/jira/browse/AMBARI-13099
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.1
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Priority: Blocker
> Fix For: 2.1.2
>
> Attachments: AMBARI-13099.patch
>
>
> Installing a cluster with a blueprint that contains host group level
> configurations are not picked up during install time. Ambari UI complains to
> restart few services after installation which doesn't make sense.
> In the provided BP there are host group level config like:
> {
> "hdfs-site" :
> { "dfs.datanode.data.dir" :
> "/hadoopfs/fs1/hdfs/datanode,/hadoopfs/fs2/hdfs/datanode" }
> },
> {
> "yarn-site" :
> { "yarn.nodemanager.local-dirs" :
> "/hadoopfs/fs1/yarn/nodemanager,/hadoopfs/fs2/yarn/nodemanager",
> "yarn.nodemanager.log-dirs" :
> "/hadoopfs/fs1/yarn/nodemanager/log,/hadoopfs/fs2/yarn/nodemanager/log" }
> }
> and those directories are not in use, but the default ones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
