Bug 1085852 - GlusterFS: Instance is not using the correct snapshot backing file after reboot
Summary: GlusterFS: Instance is not using the correct snapshot backing file after reboot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 5.0 (RHEL 7)
Assignee: Eric Harney
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On:
Blocks: 1045196 1100473
TreeView+ depends on / blocked
 
Reported: 2014-04-09 13:58 UTC by Eric Harney
Modified: 2019-09-09 14:32 UTC (History)
9 users (show)

Fixed In Version: openstack-nova-2014.1.1-1.el7ost
Doc Type: Bug Fix
Doc Text:
The GlusterFS driver changes the file name used to point to a volume when a snapshot is changed, but in the past the new file name was not stored in Compute's block device information. As a result, if the VM was shut down and started again, the old file name in the snapshot chain was used, resulting in corruption of the qcow2 chain and unexpected results in the instance. This has been fixed by persisting the new file name in Compute's block device info when a snapshot is created. Now, GlusterFS volumes work as expected after creating or deleting a snapshot and then rebooting the instance.
Clone Of:
: 1100473 (view as bug list)
Environment:
Last Closed: 2014-07-24 17:22:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1304695 0 None None None Never
OpenStack gerrit 87432 0 None None None Never
OpenStack gerrit 98255 0 None None None Never
Red Hat Product Errata RHSA-2014:0940 0 normal SHIPPED_LIVE Moderate: openstack-nova security and bug fix update 2014-07-24 21:21:42 UTC

Description Eric Harney 2014-04-09 13:58:39 UTC 
Upstream reports an issue where Nova instance shutdown/start may result in the domain pointing to the wrong backing file.  See Launchpad link for initial analysis.
Comment 7 Yogev Rabl 2014-07-23 13:27:25 UTC 
From the libvirt.xml:

<disk type="file" device="disk">
      <driver name="qemu" type="qcow2" cache="none"/>
      <source file="/var/lib/nova/mnt/e3a1bfd120fee28370d03856c402d81a/volume-d50ee694-f8eb-4284-a6a3-ac8127b28848.301f8bab-4364-4522-9329-ce67bf010c8e"/>
      <target bus="virtio" dev="vdb"/>
      <serial>d50ee694-f8eb-4284-a6a3-ac8127b28848</serial>
</disk>

verified in version:
openstack-cinder-2014.1.1-1.el7ost.noarch
python-cinder-2014.1.1-1.el7ost.noarch
python-cinderclient-1.0.9-1.el7ost.noarch
python-nova-2014.1.1-4.el7ost.noarch
openstack-nova-console-2014.1.1-4.el7ost.noarch
openstack-nova-compute-2014.1.1-4.el7ost.noarch
openstack-nova-scheduler-2014.1.1-4.el7ost.noarch
openstack-nova-api-2014.1.1-4.el7ost.noarch
openstack-nova-cert-2014.1.1-4.el7ost.noarch
python-novaclient-2.17.0-2.el7ost.noarch
openstack-nova-novncproxy-2014.1.1-4.el7ost.noarch
openstack-nova-network-2014.1.1-4.el7ost.noarch
openstack-nova-common-2014.1.1-4.el7ost.noarch
openstack-nova-conductor-2014.1.1-4.el7ost.noarch
libvirt-daemon-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-kvm-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-nodedev-1.1.1-29.el7_0.1.x86_64
libvirt-client-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-qemu-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-interface-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-config-network-1.1.1-29.el7_0.1.x86_64
libvirt-python-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-nwfilter-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-storage-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-config-nwfilter-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-secret-1.1.1-29.el7_0.1.x86_64
libvirt-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-network-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-lxc-1.1.1-29.el7_0.1.x86_64
Comment 9 errata-xmlrpc 2014-07-24 17:22:55 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0940.html
Note You need to log in before you can comment on or make changes to this bug.