instance unexpected shutdown when source node startup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Wishlist
|
zhouzhong | ||
Bug Description
Description
===========
Before shutdown the instance, the source node was breakdown, caused that the shutdown instance message remained in queue and could not be consumed, message was not consumed until the source node was started. When the source node was up, continuing to execute the stop operation, and the instance vm_state was changed to STOPPED, the periodic task of synchronized power state _sync_power_states was captured and triggered the shutdown operation.
Steps to reproduce
==================
1.create an instance
2.break down the source node of the instance, by shutdown or the others actions
3.send request to shutdown the instance
4.start the source node
Expected result
===============
The instance does not shutdown by _sync_power_states and power state is always RUNNING
Actual result
=============
The instance unexpected shutdown when the source node up
Environment
===========
| summary: |
- instance unexpected shutdown when node startup + instance unexpected shutdown when source node startup |
| Changed in nova: | |
| status: | New → In Progress |
| Changed in nova: | |
| assignee: | nobody → zhouzhong (zhouzhong) |
| zhouzhong (zhouzhong) wrote | #1 |
| sean mooney (sean-k-mooney) wrote | #2 |
| Changed in nova: | |
| importance: | Undecided → Low |
| importance: | Low → Wishlist |
I have made restrictions on all operations that may be affected by the status of the source node. The specific implementation is add the decorator "@check_
Uploaded patch at https:/
Instance unexpected shutdown when source node startup
Before shutdown the instance, the source node was breakdown, caused that
the shutdown instance message remained in queue and could not be
consumed, message was not consumed until the source node was started.
When the source node was up, continuing to execute the stop operation,
and the instance vm_state was changed to STOPPED, the periodic task of
synchronized power state _sync_power_states was captured and triggered
the shutdown operation.
Not only the instance shutdown operation, but also the operations
related to the status of the source node where the instance is located
is abnormal, the operation on the instance may cause unexpected
exceptions, so they are limited.