[Yahoo-eng-team] [Bug 1627694] Re: unshelving an instance doesn't rollback volumes connections on failure

** Also affects: nova/queens Importance: Undecided Status: New ** Changed in: nova/queens Status: New => Confirmed ** Changed in: nova/queens Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is

[Yahoo-eng-team] [Bug 1627694] Re: unshelving an instance doesn't rollback volumes connections on failure

Reviewed: https://review.openstack.org/378009 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dcdd2c9832c7c60fe9163cd744ca2b5acfe16bcc Submitter: Zuul Branch:master commit dcdd2c9832c7c60fe9163cd744ca2b5acfe16bcc Author: Shoham Peller

[Yahoo-eng-team] [Bug 1627694] Re: unshelving an instance doesn't rollback volumes connections on failure

** Also affects: nova/ocata Importance: Undecided Status: New ** Also affects: nova/pike Importance: Undecided Status: New ** Changed in: nova/ocata Status: New => Confirmed ** Changed in: nova/pike Status: New => Confirmed -- You received this bug

[Yahoo-eng-team] [Bug 1627694] Re: unshelving an instance doesn't rollback volumes connections on failure

@mriedem Thank you for your response. We don't have to detach the volume from the server, or deleting anything from the DB. The problem is simply that the volumes are stayed connected to the node, because initialize_connection was called, but when spawning failed, and the VM is not on the node,

[Yahoo-eng-team] [Bug 1627694] Re: unshelving an instance doesn't rollback volumes connections on failure

So I'm actually not sure about this bug. When shelve-offloading an instance, the instance is destroyed from the hypervisor but the network and volumes are left intact for the instance in the database. When we unshelve the instance, network and volume information is still available in neutron and