Instance is stopped on destination node after evacuation if stop call was issued before evacuation
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Medium
|
Alexey Stupnikov | ||
Bug Description
Steps to reproduce:
1. Start an instance on a compute node (src compute).
2. Destroy src compute. Wait till nova-compute server will go down.
3. Run 'openstack server stop' for an instance.
4. Run 'server set --state error' to the instance to be able to evacuate the instance (no longer needed if fix for bug #1978983 presents)
5. Evacuate the instance to another compute node (dst compute).
6. Start src compute.
7. Confirm that the evacuated instance is stopped after src compute come online.
This behavior is a bug because src compute could come up after few months and shutdown some important instance. It looks like this behavior is caused by cast RPC call for SRC compute to stop an instance which sits in the queue until compute is back online and then causes DB state change.
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to nova (master) | #1 |
| Balazs Gibizer (balazs-gibizer) wrote | #2 |
| Changed in nova: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| tags: | added: evacuate |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #3 |
Related fix proposed to branch: master
Review: https:/