NetApp ONTAP Cinder driver has support for setting QoS. 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). When a migrate operation is issued, the QoS policy group is deleted. Steps to reproduce: - Set up 2 ONTAP back ends `ontap1` and `ontap2` - Create a Cinder QoS `qos_test` - Create a Cinder volume type `ontap` - Associate the QoS `qos_test` to the volume type `ontap` - Create a Cinder volume with the volume type `ontap` - Migrate the volume to another ONTAP back end - Wait for the driver to perform a host-assited migration - Wait for the driver to create a new QoS policy group and associate it to the new LUN/file representing the volume Expected result: - Have the new QoS policy group associated to the LUN/file permanently. Actual result: - The new QoS policy group is deleted afer a few minutes. Detailed commands and outputs are here [0]. [0] http://paste.openstack.org/show/800563/
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 (Red Hat OpenStack Platform 16.1.9 bug fix and enhancement 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. https://access.redhat.com/errata/RHBA-2022:8795
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days