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. ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1774363 Title: Instance is of no use during "shelve-offloading" operation, when nova- conductor is stopped Status in OpenStack Compute (nova): Invalid 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_OFFLOADING" state. 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_OFFLOADING" state. In this particular state, the instance is of no use because an instance cannot shelve, unshelve and shelve-offload. Source code should be modified to reset the state of instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1774363/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
