[AMBARI-10524] Ambari blueprints generated by the API do not update all hostgroups

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.3.0
• Component/s: blueprints
• Assignee: Unassigned
• Reporter: Charles Llewellyn
• Created: 16/Apr/15 14:13
• Updated: 16/Apr/15 14:35
• Resolved: 16/Apr/15 14:35

Description

Steps to produce.

1. Create a cluster via the Ambari UI. The cluster consists of dedicated three zookeeper servers, three slave nodes and two master nodes.
2. Generate a new blueprint via the API:
curl -u admin:'admin' -i -H 'X-Requested-By: ambari' -X GET http://192.168.0.2:8080/api/v1/clusters/testCluster?format=blueprint
3. Inspecting the blueprint shows static hostname entries for the following keys:
"yarn.resourcemanager.webapp.https.address"
"yarn.resourcemanager.zk-address"
e.g. "yarn.resourcemanager.zk-address" : "zk.host1.hdplab.com:2181"

I believe the references should be generic like "yarn.resourcemanager.zk-address" : "%HOSTGROUP::host_group_2%:2181"