associate qos specs with type already associated overwirtes orginal association
Bug #1222692 reported by
Huang Zhiteng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Huang Zhiteng |
Bug Description
When trying to associate a volume type T1, which is already associated with QoS Specs Q1, with Q2, current implementation doesn't
give any error and will overwrite the association with newly requested relation.
How to reproduce:
1. create two qos specs (Q1, Q2) and volume type (T1);
2. associate T1 with Q1;
3. associate T1 with Q2;
Current result: T1 is associated with Q2 after step 3; expected result: T1 is still associated with Q1, error raises.
Changed in cinder: | |
assignee: | nobody → Huang Zhiteng (zhiteng-huang) |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → havana-rc1 |
Changed in cinder: | |
status: | Confirmed → Fix Committed |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/45635
Review: https:/