Nova delayed instance lifecycle events issue
Bug #1468431 reported by
Lucian Petrut
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Lucian Petrut | ||
Bug Description
The instance lifecylcle events can be delayed, thus not reflecting the current instance power state.
Some drivers may power off/on the instance during operations such as rescue or resize. If the event is handled by the manager after the operation finishes and the instance task state is set to "None", the manager can attempt to call the stop API, even if the instance is currently active.
| Changed in nova: | |
| assignee: | nobody → Lucian Petrut (petrutlucian94) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → liberty-3 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | liberty-3 → 12.0.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit f28359a15d5f21a
Author: Lucian Petrut <email address hidden>
Date: Wed Jun 24 04:50:48 2015 +0300
Fixes delayed instance lifecycle events issue
The instance lifecycle events can be delayed, thus not reflecting
the current instance power state.
This patch fixes the manager lifecycle event handling by adding an
extra check, verifying against the current instance power state.
In case there is a mismatch, it is safe to ignore the event as
there should be another one, signaling the transition to the
current state.
Change-Id: I7f3bf9ee9e40ec
Closes-Bug: #1468431