Unshelve instance needs handling exceptions
Bug #1307416 reported by
Sahid Orentino
This bug affects 6 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Low
|
Sahid Orentino | ||
Bug Description
There are some error cases not handled when we unshelve an instance in the conductor.
nova/
if the key 'shelved_image_id' is not defined the current code will raise an KeyError not handled.
Also when the 'shelved_image_id' is set to None (which is not the expected behavior), the error is not correctly handled and the message could be confusing.
| description: | updated |
| tags: | added: conductor |
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 → juno-rc1 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit c58f2393b1c8826
Author: Sahid Orentino Ferdjaoui <email address hidden>
Date: Thu Apr 24 18:57:44 2014 +0200
Improve conductor error cases when unshelving
This commit handles different cases when the key 'shelved_image_id'
is not defined or None. Also it tries to improve the error messages.
Closes-Bug: #1307416
Change-Id: Ia2d0a183eefccd