cinder/netapp-migrated-qos-c0c8aae50d010c75.yaml at a97fd2369395a32236e6064d82eddf3cc3aed6e8 - cinder - OpenDev: Free Software Needs Free Tools

openstack/cinder

Gorka Eguileor da100e1fca NetApp ONTAP: Fix QoS lost after moving volume

When a Cinder volume is created with a volume-type associated to a QoS
entity, the driver creates a QoS policy group at the ONTAP back end, and
associates it to the entity representing the Cinder volume (either a LUN
or a file within an NFS share).

On NetApp NFS, when a migrate operation is issued and it completes, the
resulting volume ends up without a QoS.  That happens because the file
is being renamed while the QoS refers to the now non-existent file.

This patch makes it so that the file is not renamed when finishing a
migration and the driver code uses the ``name_id`` attribute instead of
the ``id`` one to refer to the right UUID.

Closes-Bug: #1906291
Change-Id: Icd7a929e7cbce0c74f6b340f4e09f74a8098d752

2021-06-10 11:18:37 +02:00

8 lines

234 B

YAML

Raw Blame History

 ---
 fixes:
   - |
     NetApp ONTAP `bug #1906291
     <https://bugs.launchpad.net/cinder/+bug/1906291>`_: Fix volume losing its
     QoS policy on the backend after moving it (migrate or retype with migrate)
     to a NetApp NFS backend.