yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #20668
[Bug 1366166] Re: Private flavor update with horizon will cause access issue of existed instances
Closing per comment 2
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1366166
Title:
Private flavor update with horizon will cause access issue of existed
instances
Status in OpenStack Dashboard (Horizon):
Invalid
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://bugs.launchpad.net/horizon/+bug/1276371
one quick solution is mark deleted flavor as public in nova
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1366166/+subscriptions
References