Resize Flavor Validation Overly Restrictive, Blocks VCPU Increase + More
Bug #1382931 reported by
Auston McReynolds
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Davide Agnello |
Bug Description
the resize instance validation is overly restrictive. in short, the resize instance operation should be permitted if the new flavor id is different than the old flavor id.
why: even if the ram, cpu, and root disk are the same, a flavor can have scheduler hints placed on it.
the logic today blocks these very valid scenarios:
(1) resize to a flavor with more vcpus, but the same amount of ram
(2) resize to a flavor with the same amount of ram + vcpus, but more root-disk.
(3) resize to a flavor with the same ram + vcpus + root-or-ephemeral, but different flavor-id.
(4) etc.
summary: |
- Resize Flavor Validation Overly Restrictive + Resize Flavor Validation Overly Restrictive, Blocks VCPU Increase + More |
Changed in trove: | |
milestone: | kilo-1 → kilo-2 |
Changed in trove: | |
milestone: | kilo-2 → kilo-3 |
Changed in trove: | |
assignee: | nobody → Nikhil Manchanda (slicknik) |
Changed in trove: | |
assignee: | Nikhil Manchanda (slicknik) → Saurabh Surana (saurabh-surana) |
Changed in trove: | |
assignee: | Saurabh Surana (saurabh-surana) → Davide Agnello (dagnello) |
Changed in trove: | |
status: | Triaged → In Progress |
Changed in trove: | |
milestone: | kilo-3 → kilo-rc1 |
Changed in trove: | |
status: | In Progress → Fix Committed |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
i'm leaving this unassigned at the moment because i'm working on a few other bugs; if anyone is interested in fixing this, go for it.