MOS9, sometimes, when run "deploy-change", fuel specifies random nodes for provision
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Sustaining |
Bug Description
I have seen this at least twice on a customer site in different DCs.
For example, in a deployed environment, they want to run deploy-change to fix one compute host, which is in error status. However, fuel marks 4 other nodes, which were in ready status to be provisioned. Those 4 nodes have Openstack installed.
Fuel does not allow to run "deployment" only, we have to use "provision + deployment". Then, we have to PXE boot and re-provision those 4 nodes, in order to fix one node in error status.
This is a very serious problem.
Steps I was able to reproduce it with:
1. In a ready environment,
2. make one node offline,
3. do a deploy-changes to add a new node or delete a node, whatever
4. the deployment will fail with error , because of the offline node.
5. Run deploy-changes again, Fuel will re-provision that node.
description: | updated |
description: | updated |
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
milestone: | none → 9.2 |
I have seen it again. It should be easy to reproduce.
1. In a ready environment,
2. make one node offline,
3. do a deploy-changes to add a new node or delete a node, whatever
4. the deployment will fail with error , because of the offline node.
5. Run deploy-changes again, Fuel will re-provision that node.