test_volume_boot_pattern tempest test failure for glusterfs backend - Part 2

[Deepak C Shetty]

This bug is in continuation of https://bugs.launchpad.net/cinder/+bug/1441050 (Part 1 of the problem)

This bug is opened to track the 2nd issue that GlusterFS (and in future any FS backed driver that uses hyp assisted snapshot) is hitting.

Refer to comment nos: #5 (No. 2) , #6, #8, #10 of https://bugs.launchpad.net/cinder/+bug/1441050 for more details

In short, the testcase tries to delete the snapshot after the VM is OFF, which libvirt yet doesn't support for external snapshots, thus the excp seen as below :

2015-04-08 07:22:44.376 32701 TRACE nova.virt.libvirt.driver File "/usr/local/lib/python2.7/dist-packages/libvirt.py", line 792, in blockRebase
2015-04-08 07:22:44.376 32701 TRACE nova.virt.libvirt.driver if ret == -1: raise libvirtError ('virDomainBlockRebase() failed', dom=self)
2015-04-08 07:22:44.376 32701 TRACE nova.virt.libvirt.driver libvirtError: Requested operation is not valid: domain is not running
2015-04-08 07:22:44.376 32701 TRACE nova.virt.libvirt.driver

Some mailing list discussion around this issue is available at:
http://lists.openstack.org/pipermail/openstack-dev/2015-April/060983.html

This bug is opened to track this issue to figure whether we wait for libvirt support or change Nova-Cinder interactions to better handle this scenario ?

Due to this, the Cinder-GlusterFS CI job (check-tempest-dsvm-full-glusterfs-nv) is failing, which was otherwise running successfully for several weeks.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/192736
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1cf793df252756615dc01a105953346a8747e755
Submitter: Jenkins
Branch: master

commit 1cf793df252756615dc01a105953346a8747e755
Author: Jordan Pittier <email address hidden>
Date: Wed Jul 15 14:07:29 2015 +0200

    libvirt:on snapshot delete, use qemu-img to blockRebase if VM is stopped

    Libvirt won't do a blockRebase on a domain that is not running. So,
    in that case, use "qemu-img rebase" instead.

    Note: For now, trying to rebase a network disk using qemu-img raises
    a NovaException error because I can't test that it successfully works
    for every protocol (gluster, sheepdog, etc) that executes this code
    path. I successfully tested this with file-based disk.

    Change-Id: I0e6819a6c8dc70b9bd7d1a9c18dc185b4537a3e4
    Closes-Bug: #1444806
    Closes-Bug: #1465416

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/243028

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/nova 13.0.0.0b1 development milestone.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/243028
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aea87902180bebae93680e156a950f00a5f360fd
Submitter: Jenkins
Branch: stable/liberty

commit aea87902180bebae93680e156a950f00a5f360fd
Author: Jordan Pittier <email address hidden>
Date: Wed Jul 15 14:07:29 2015 +0200

    libvirt:on snapshot delete, use qemu-img to blockRebase if VM is stopped

    Libvirt won't do a blockRebase on a domain that is not running. So,
    in that case, use "qemu-img rebase" instead.

    Note: For now, trying to rebase a network disk using qemu-img raises
    a NovaException error because I can't test that it successfully works
    for every protocol (gluster, sheepdog, etc) that executes this code
    path. I successfully tested this with file-based disk.

    Change-Id: I0e6819a6c8dc70b9bd7d1a9c18dc185b4537a3e4
    Closes-Bug: #1444806
    Closes-Bug: #1465416
    (cherry picked from commit 1cf793df252756615dc01a105953346a8747e755)

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/nova 12.0.1 release.