| 2017-01-20 00:32:22 |
ZHI BING WANG |
bug |
|
|
added bug |
| 2017-01-20 00:33:24 |
ZHI BING WANG |
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, where 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. |
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. |
|
| 2017-01-20 00:42:26 |
ZHI BING WANG |
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. |
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.
There are many people working on those sites, I am not sure what happened, and what's the procedure to reproduce it. |
|
| 2017-01-20 08:04:52 |
Julia Aranovich |
fuel: assignee |
|
Fuel Sustaining (fuel-sustaining-team) |
|
| 2017-01-20 08:04:56 |
Julia Aranovich |
fuel: milestone |
|
9.2 |
|
| 2017-01-23 22:18:46 |
Sam Stoelinga |
tags |
|
customer-found |
|
| 2017-01-23 22:19:23 |
Sam Stoelinga |
fuel: importance |
Undecided |
High |
|
| 2017-01-23 22:23:05 |
Sam Stoelinga |
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.
There are many people working on those sites, I am not sure what happened, and what's the procedure to reproduce it. |
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. |
|
| 2017-01-24 09:54:01 |
Oleksiy Molchanov |
fuel: status |
New |
Invalid |
|
