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

["Robert Nettleton (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Nettleton resolved AMBARI-10524.
---------------------------------------
    Resolution: Duplicate

AMBARI-10411 already tracks many of the Blueprint export issues related to Yarn configuration, so I've updated that bug to include the property mentioned here, and am closing this issue as a duplicate of AMBARI-10411.  

> Ambari blueprints generated by the API do not update all hostgroups
> -------------------------------------------------------------------
>
>                 Key: AMBARI-10524
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10524
>             Project: Ambari
>          Issue Type: Bug
>          Components: blueprints
>    Affects Versions: 2.2.0
>            Reporter: Charles Llewellyn
>            Priority: Minor
>
> 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"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)