Private flavor update with horizon will cause access issue of existed instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Julie Pichon | ||
Juno |
Fix Released
|
Medium
|
Julie Pichon |
Bug Description
How to reproduce
1. create a private flavor "private-flavor"
2. add a tenant access to "private-flavor"
3. use regular user to create instance "XXX" with "private-flavor"
4. add/remove tenant access to the "private-flavor" via horizon
5. nova show XXX, will be end with error message say do not have access to the flavor
Root cause,
add/remove tenant access to the "private-flavor" via horizon. will do delete old one which will also delete the access to the old flavor, create new one with the same configuration, and add accesses back to the new flavor.
The version before H3, horizon will pass flavor uuid to backend then will create new flavor with the same uuid, that's why it didn't cause problem, but it also cause another bug https:/
one quick solution is mark deleted flavor as public in nova
Changed in horizon: | |
assignee: | nobody → Wei T (nuaafe) |
Changed in horizon: | |
milestone: | none → kilo-1 |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | kilo-1 → 2015.1.0 |
Related to https:/ /bugs.launchpad .net/nova/ +bug/1366168