yahoo-eng-team team mailing list archive

[Zhenyu Zheng <zhengzhenyu@xxxxxxxxxx>]

Public bug reported:

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".

** Affects: horizon
     Importance: Undecided
         Status: New

** Description changed:

- 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.
+ 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".
+ 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".

-- 
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):
  New

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