IBM Storwize: unable to retype to the new qos, if QoS is empty
Bug #1368595 reported by
Vincent Hou
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Vincent Hou |
Bug Description
QoS should be changed after retyping the volume.
So far for storwzie driver, if the new type does not have QoS configurations, the old QoS configurations remain in the volume.
Changed in cinder: | |
assignee: | nobody → Vincent Hou (houshengbo) |
tags: | added: drivers storwize |
Changed in cinder: | |
milestone: | none → juno-rc1 |
status: | Fix Committed → Fix Released |
milestone: | juno-rc1 → none |
status: | Fix Released → Fix Committed |
Changed in cinder: | |
milestone: | none → juno-rc2 |
Changed in cinder: | |
importance: | Undecided → Medium |
Changed in cinder: | |
milestone: | juno-rc2 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/121022
Review: https:/