Edit Flavor Window Displays Details of Deleted Flavors

Bug #1100444 reported by Sean Carlisle
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Invalid
High
Gabriel Hurley
Folsom
Won't Fix
Medium
Unassigned

Bug Description

A user deletes all existing flavors and creates new flavors. When they click the "Edit Flavors" button, the window displays the details of the deleted flavor of the same flavor ID. This window appears to disregard the deleted flag in the table nova.instance_types and pulls the first row that matches the flavor ID.

Steps to reproduce:

1.) Delete all existing flavors.
2.) Create a new flavor through the dashboard.
3.) Once the flavor has been created, click the "Edit Flavor" button.

Thank you,

Sean Carlisle

Changed in horizon:
importance: Undecided → High
milestone: none → grizzly-3
status: New → Confirmed
Revision history for this message
Tony NIU (niuwl586-v) wrote :

It is a bug of nova-api. When dashboard call api "v2/{tenant_id}/flavors/{flavor_id}", nova-api return the deleted flavor infomation.

Revision history for this message
Kieran Spear (kspear) wrote :

@Sean: Are you using the Folsom release? I can repro on Folsom Horizon but not on master.

I'm pretty sure this was fixed when Horizon switched to using UUIDs for flavor ids in:

https://review.openstack.org/#/c/14787/

Using a string for flavor id seems to be supported by Nova stable/folsom, so probably a good candidate for backporting.

Revision history for this message
Sean Carlisle (sean-carlisle) wrote :

@Kieran: Yes this is with the Folsom release. However, I think Tony is correct about the bug existing in the Nova API. I was just able to recreate the issue by deleting a flavor, creating a new one with the same flavor ID using Nova CLI, then used curl to retrieve the description of that flavor ID.

Revision history for this message
Kieran Spear (kspear) wrote :

@Sean: Yeah, looks like it. I think there are some cases that need to get a deleted flavor (e.g., if it's still referenced by an existing instance). But there's no way to tell the API to exclude it when retrieving a flavor by id, and it would seem there's also no way to tell whether an instance is tied to the new or old flavor if IDs are the same.

I'll ask openstack-dev.

Revision history for this message
Masayuki Igawa (igawa) wrote :

I'm facing the same issue in Folsom. So I've added 'folsom-backport-potential' tag to bug 1057799 .

By the way, I noticed the codes of generating uuid was removed by bug 1076761 in master.
Should we add 'folsom-backportable' tag to bug 1076761 ?

Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

Sounds like this is only present in Folsom at this point. I've retargeted the bug.

Changed in horizon:
assignee: nobody → Gabriel Hurley (gabriel-hurley)
milestone: grizzly-3 → none
status: Confirmed → Invalid
Revision history for this message
Ryan Richard (ryan-richard) wrote :

I guess the main problem is that flavors that are being used are allowed to be deleted and the allowing the creation of new flavors with the same IF as another.

Perhaps the original idea was to allow the deletion of a flavor so no instances could use that flavor but running instances built from that flavor still need to have that relationship in the database.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers