Instance is of no use during "shelve-offloading" operation, when nova-conductor is stopped
Bug #1774363 reported by
Swati Bansal
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned |
Bug Description
During shelve-offloading operation if nova-conductor is stopped, the instance stuck forever in "SHELVED" state and task state of instance stuck in "SHELVING_
After restarting the nova-conductor service, the state of instance does not change to "SHELVE_OFFLOADED" from "SHELVED" and the task state remains in "SHELVING_
Source code should be modified to reset the state of instance.
tags: | added: shelve |
tags: | added: conductor |
Changed in nova: | |
status: | Invalid → New |
To post a comment you must log in.
Everything goes through nova-conductor for database updates so if that's down, you have problems. You can reset the state of the instance using the reset state API (as admin):
https:/ /docs.openstack .org/python- openstackclient /latest/ cli/command- objects/ server. html#server- set
nova server set --state error
Although you can't unshelve from that if the instance is really offloaded and not on a host. If the shelve offload image snapshot was successful, then you basically need to delete the old server and create a new one from the shelved offloaded image snapshot.