[Bug 981269] [NEW] instance_type is still set as a property value of "none" even when flavors cannot be retrieved
Launchpad Bug Tracker
981269 at bugs.launchpad.net
Fri Jan 25 17:00:58 UTC 2013
You have been subscribed to a public bug by Yaguang Tang (heut2008):
[Impact]
* horizon throw errors when view horizon/syspanel/instances/ page with deleted
flavor still in use by instances.
* try to get flavor info through the flavor.get api,this can retrive the deleted
flavor info.
[Test Case]
* Launch an instance of flavor m1.tiny
on controller node do: nova flavor-delete m1.tiny, and wait for it to succeed.
on horizon look at the state of the machines, http://horizon-system:port/horizon/
syspanel/instances/ and wait for it to fail because horizon can not find the flavor
m1.tiny and therefore can not report the status and details of the instance in
question.
[Regression Potential]
* This is a backport from upstream.
In Nova dashboard and Syspanel dashboard if the flavor of an instance
cannot be retrieved the property .full_flavor will still be set to
"None". If there is no error retrieving flavors and a flavor has been
deleted, this can cause a large traceback in the table rendering as
get_size checks if the instance object hasattr() "full_flavor" instead
of for the individual values to display in the "Size" column.
Attached is a potential fix. I have also included an alternate code
path that will directly query the API for a flavor's information if it
is not present in the full_flavors list(); this can occur if a flavor
has been deleted as api.nova.flavors_list() only returns flavors that
are not deleted.
** Affects: horizon
Importance: Medium
Assignee: Ke Wu (ke-wu)
Status: Fix Released
** Affects: openstack-dashboard (Ubuntu)
Importance: Medium
Assignee: Yaguang Tang (heut2008)
Status: In Progress
** Tags: deleted flavors patch
--
instance_type is still set as a property value of "none" even when flavors cannot be retrieved
https://bugs.launchpad.net/bugs/981269
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list