[AMBARI-13099] Host group level config changes are not picked up with Blueprint provisioning

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.1.1
• Fix Version/s: 2.1.2
• Component/s: ambari-server
• Assignee: Oliver Szabo
• Reporter: Oliver Szabo
• Created: 15/Sep/15 10:48
• Updated: 18/Sep/15 03:50
• Resolved: 18/Sep/15 00:13

Description

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.

Issue Links

• links to: Review Board