Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
We submit blueprint with configurations (core-site):
{"Blueprints":
{ "blueprint_name": "bp1_simple", "stack_name": "HDP", "stack_version": "2.2" },
"host_groups": [
{
"name": "master_1",
"cardinality" : "1",
"components": [
,
,
,
,
,
,
,
,
,
{ "name": "ZOOKEEPER_CLIENT" } ]
},
{
"name": "master_2",
"cardinality" : "1",
"components": [
,
,
,
,
,
{ "name": "NODEMANAGER" } ]
},
{
"name": "master_3",
"cardinality" : "1",
"components": [
,
,
,
,
,
,
{ "name": "NODEMANAGER" } ]
}
}
"configurations": [
{
"core-site": {
"properties" : {
"fs.defaultFS" : "hdfs://mycluster",
"ha.zookeeper.quorum" : "%HOSTGROUP::master_1%:2181,%HOSTGROUP::master_2%:2181,%HOSTGROUP::master_3%:2181"
}}
}
]
}
After "cluster assign" and "cluster create". The ambari-server still has the "%HOSTGROUP::master_1%" in corresponding hostname position and did not translate them.
We checked database those configs are added to table "blueprint-configuration" once the blueprint is added and never have chance to be changed even we change some "%HOSTGROUP::master_1%" to correct hostname through Ambari webUI.