yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #67040
[Bug 1708323] Re: Editing flavor causing instance flavor display error
*** This bug is a duplicate of bug 1709056 ***
https://bugs.launchpad.net/bugs/1709056
This issue was addressed in bug 1709056. It added a setting to disable
the edit flavor by default and the feature will be removed in R release
cycle.
** This bug has been marked a duplicate of bug 1709056
Nova doesn't actually allow editing flavors, but Horizon does. This breaks things.
--
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/1708323
Title:
Editing flavor causing instance flavor display error
Status in OpenStack Dashboard (Horizon):
Confirmed
Bug description:
Horizon provided the feature to allow user edit existing flavors, no
matter it is currently used by any instances or not. While Nova
doesn't provide this kind of ability, Horizon achieved this by
deleting the old flavor first and create a new flavor with the
requested properties. And the flavor ID will be changed to a new UUID.
This causes problem when display instances with latest Nova, Horizon
display flavor name by request flavor details using the flavor id
returned by get_instance request, because Nova now moved flavor to
api_db, and when a flavor got deleted, it will be directly removed
from the DB, and when displaying, the field will be "Not Available".
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1708323/+subscriptions
References