PowerMax - QoS should not be set on parent storage group

Bug #1930290 reported by Helen Walsh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
Unassigned

Bug Description

The parent storage group is just a hold all for the child
storage groups which contain the attributes service level and QoS.
Setting QoS on the parent storage
group can cause problems as having a higher I/O limit on the
child than the parent is not allowed and this is not the
intention.

PowerMax only bug

Error received:
Exception received was Error modify storagegroup resource. The status code received is 500 and the message is {'message': "A problem occurred modifying the storage group resource: Error Adding items to Storage Group 'OS-myhost-F-OS_PG-SG': The operation cannot be performed because the storage group attribute conflicts with other parent or child storage group attribute"}.:

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/cinder/+/793814

Changed in cinder:
status: New → In Progress
Changed in cinder:
importance: Undecided → Medium
tags: added: powermax qos
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.opendev.org/c/openstack/cinder/+/793814
Committed: https://opendev.org/openstack/cinder/commit/1084de1f1666c2c5e9a850ef39c124bf74652dad
Submitter: "Zuul (22348)"
Branch: master

commit 1084de1f1666c2c5e9a850ef39c124bf74652dad
Author: Helen Walsh <email address hidden>
Date: Mon May 31 16:37:12 2021 +0100

    PowerMax Driver - QoS should not be set on parent storage group

    The parent storage group is just a hold all for the child
    storage groups which contain attributes like service level and QoS.
    Setting QoS on the parent storage group can cause problems as
    having a higher I/O limit on the child than the parent is not
    allowed and this is not the intention. The fix is to set
    QoS on the child storage groups only.

    Closes-Bug: #1930290
    Change-Id: Ib2c1a44086da1fa3c64611344221c9307be22296

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (stable/xena)

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/cinder/+/821745

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 20.0.0.0rc1

This issue was fixed in the openstack/cinder 20.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (stable/xena)

Reviewed: https://review.opendev.org/c/openstack/cinder/+/821745
Committed: https://opendev.org/openstack/cinder/commit/6e3fd9e8f7a03f64f48a9ae62f24308bbb302882
Submitter: "Zuul (22348)"
Branch: stable/xena

commit 6e3fd9e8f7a03f64f48a9ae62f24308bbb302882
Author: Helen Walsh <email address hidden>
Date: Mon May 31 16:37:12 2021 +0100

    PowerMax Driver - QoS should not be set on parent storage group

    The parent storage group is just a hold all for the child
    storage groups which contain attributes like service level and QoS.
    Setting QoS on the parent storage group can cause problems as
    having a higher I/O limit on the child than the parent is not
    allowed and this is not the intention. The fix is to set
    QoS on the child storage groups only.

    Closes-Bug: #1930290
    Change-Id: Ib2c1a44086da1fa3c64611344221c9307be22296
    (cherry picked from commit 1084de1f1666c2c5e9a850ef39c124bf74652dad)

tags: added: in-stable-xena
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 19.2.0

This issue was fixed in the openstack/cinder 19.2.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.