Reviewed: https://review.openstack.org/257275
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=e89e1bdc60211622440c964f8be8563da89341ac
Submitter: Jenkins
Branch: master
commit e89e1bdc60211622440c964f8be8563da89341ac
Author: Andrea Rosa <andrea.r...@hp.com>
Date: Thu Sep 14 13:47:06 2017 -0400
Call terminate_connection when shelve_offloading
When nova performs a shelve offload for an instance, it needs to terminate
all the volume connections for that instance as with the shelve offload
it is not guaranteed that the instance will be placed on the same host once
it gets unshelved.
This change adds the call to the terminate_volume_connections on the
_shelve_offload_instance method in the compute manager.
Closes-Bug: #1547142
Change-Id: I8849ae0f54605e003d5b294ca3d66dcef89d7d27
** Changed in: nova
Status: In Progress => Fix Released
--
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/1547142
Title:
A shelved_offload VM's volumes are still attached to a host
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) ocata series:
Confirmed
Status in OpenStack Compute (nova) pike series:
In Progress
Bug description:
When shelve_offloading a VM, the VM loses it's connection to a host.
However, connection to the host is not terminated to it's volumes, so they
are still attached to a host.
Afterwards, when the VM is unshleved, nova calls initialize_connection
to the new host for it's volumes, and they are now connected to 2
hosts.
The correct behaviour is to call terminate_connection on the VM's
volumes when it's being shelved_offloaded
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1547142/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
