Hiera nodes.yaml is out of date after removing a node
Bug #1491027 reported by
Swann Croiset
This bug report is a duplicate of:
Bug #1485505: custom roles cannot update other nodes on deletion.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Undecided
|
Ihor Kalnytskyi |
Bug Description
Steps to reproduce:
1/ deploy 1 controller and 2 compute nodes
2/ remove one compute node
Expected results:
after step #2, /etc/hiera/
Actual results:
after step #2, /etc/hiera/
Other informations:
if a new compute node is added to the cluster, the nodes.yaml is correctly updated, this behavior must be the same when scaling down the cluster.
To post a comment you must log in.
This is a duplicate of https:/ /bugs.launchpad .net/bugs/ 1485505 because update_required parameter in a role definition only gets applied on all relevant nodes during node addition/ reprovision, but not on node removal. There is an exception for removing controllers that is hardcoded, but it should apply to any role that has this update_required flag set.