overcloud deploy command calls ansible-playbook always with "--limit !"
Bug #1785597 reported by
Jose Luis Franco
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Jose Luis Franco |
Bug Description
When deploying the overcloud the mistral workflow tripleo.deploying is being called. At the same time, this workflow makes use of the tripleo.
To post a comment you must log in.
When calling the action used to get the blacklisted_ hostnames argument, this is what we get: (undercloud) [zuul@subnode-0 ~]$ openstack action execution run heat.stacks_ output_ show '{"stack_id" : "overcloud", "output_key" : "BlacklistedHos tnames" }' tnames" , "description": "List of blacklisted hostnames"}}}
{"result": {"output": {"output_value": [""], "output_key": "BlacklistedHos
So, self.blackliste d_hostnames is by default [""] if not BlacklistedHost names were defined for the role.