Instances erroneously still running in XenServer
Bug #911366 reported by
Rick Harris
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When running XenServer (but possibly on other hypervisors as well), over time, it's possible to enter a state where the database shows an instance as deleted but that instance is still running on the host machine.
This is a placeholder bug to figure out what the root cause is, and to fix it.
As a stop-gap, https:/
| Changed in nova: | |
| 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: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit e695b8498c486d5
Author: Rick Harris <email address hidden>
Date: Wed Dec 21 22:40:23 2011 +0000
Adds running_
This adds a periodic task to cleanup erroneously running instances. The
impetus of the patch was a XenServer specific issue bug #911366, where deleted
instances would remain running on the host machine.
The patch however is hypervisor agnostic and is generally useful as a
housekeeping task to make sure these 'zombied' instances are detected.
Change-Id: Iddc6a88920a537