yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #54345
[Bug 1583284] Re: disconnect_volume calls are made during a remote rebuild of a volume backed instance
Reviewed: https://review.openstack.org/318266
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fdf3328107e53f1c5578c2e4dfbad78d832b01c6
Submitter: Jenkins
Branch: master
commit fdf3328107e53f1c5578c2e4dfbad78d832b01c6
Author: Lee Yarwood <lyarwood@xxxxxxxxxx>
Date: Wed May 18 17:11:16 2016 +0100
compute: Skip driver detach calls for non local instances
Only call for a driver detach from a volume if the instance is currently
associated with the local compute host. This avoids potential virt
driver and volume backend issues when attempting to disconnect from
volumes that have never been connected to from the current host.
Closes-Bug: #1583284
Change-Id: I36b8532554d75b24130f456a35acd0be838b62d6
** 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/1583284
Title:
disconnect_volume calls are made during a remote rebuild of a volume
backed instance
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Description
===========
disconnect_volume calls are made during a remote rebuild of a volume backed instance
Steps to reproduce
==================
- Evacuate a volume backed instance.
- disconnect_volume is called for each previously attached volume on the now remote node rebuilding the instance.
Expected result
===============
disconnect_volume is not called unless the instance was previously running on the current host.
Actual result
=============
disconnect_volume is called regardless of the instance previously running on the current host.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://docs.openstack.org/releases/
Multinode devstack
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
libvirt + KVM
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
LVM/iSCSI
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1583284/+subscriptions
References