This bug was fixed in the package nova - 2:19.0.0-0ubuntu5
---------------
nova (2:19.0.0-0ubuntu5) eoan; urgency=medium
* d/p/bug_1825882.patch: Cherry-picked from upstream to ensure
virsh disk attach does not fail silently (LP: #1825882).
* d/p/bug_1826523.patch: Cherry-picked from upstream to ensure
always disconnect volumes after libvirt exceptions (LP: #1826523).
-- Sahid Orentino Ferdjaoui <sahid.ferdja...@canonical.com> Thu, 16
May 2019 10:41:27 +0200
** Changed in: nova (Ubuntu)
Status: Triaged => 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/1826523
Title:
libvirtError exceptions during volume attach leave volume connected to
host
Status in Ubuntu Cloud Archive:
Fix Committed
Status in Ubuntu Cloud Archive queens series:
Triaged
Status in Ubuntu Cloud Archive rocky series:
Triaged
Status in Ubuntu Cloud Archive stein series:
Fix Committed
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) queens series:
Fix Committed
Status in OpenStack Compute (nova) rocky series:
Fix Committed
Status in OpenStack Compute (nova) stein series:
Fix Committed
Status in nova package in Ubuntu:
Fix Released
Status in nova source package in Bionic:
Triaged
Status in nova source package in Cosmic:
Fix Committed
Status in nova source package in Disco:
Fix Committed
Bug description:
[Impact]
* This is an additional patch required for bug #1825882, when
a libvirt exception that prevents the volume attachment to complete,
the underlying volumes should be disconnected from the host.
[Test Case]
* Deploy any OpenStack version up to Pike , which includes ceph backed cinder
* Create a guest VM (openstack server ...)
* Create a test cinder volume
$ openstack volume create test --size 10
* Force a drop on ceph traffic. Run the following command on the nova
hypervisor on which the server runs.
$ iptables -A OUTPUT -d ceph-mon-addr -p tcp --dport 6800 -j DROP
* Attach the volume to a running instance.
$ openstack server add volume 7151f507-a6b7-4f6d-a4cc-fd223d9feb5d
742ff117-21ae-4d1b-a52b-5b37955716ff
* This should cause the volume attachment to fail
$ virsh domblklist instance-xxxxx
Target Source
------------------------------------------------
vda nova/7151f507-a6b7-4f6d-a4cc-fd223d9feb5d_disk
No volume should attached after this step.
* If the behavior is fixed:
* Check that openstack server show , doesn't displays the
displays the volume as attached.
* If the behavior isn't fixed:
* openstack server show <ID> , will display the volume in the
volumes_attached property.
[Expected result]
* Volume attach fails and the volume is disconnected from the host.
[Actual result]
* Volume attach fails but remains connected to the host.
[Regression Potential]
* The patches have been cherry-picked from upstream which helps to
reduce the regression potential of these fixes.
[Other Info]
* N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1826523/+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
