flavours that are in use can be deleted

Bug #1820790 reported by Wouter van Bommel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

It is possible to remove a instance flavour while instances of that type are still active in the cloud.
This does result in all kind of strange symptoms like not being able to resize the instance etc.

Flavours that are actively in used by an instance in the could should not be removable via the api's.

tags: added: canonical-bootstack
Revision history for this message
Matt Riedemann (mriedem) wrote :

What release are you using? The flavor used to create an instance (and last resize it) are embedded in the database with the instance (see the instance_extra.flavor entry in the DB). If you are having issues because of deleting flavors that some servers are using, you might just be on a very old release that is not using the embedded flavors properly (like Juno or older?).

Changed in nova:
status: New → Incomplete
Revision history for this message
Wouter van Bommel (woutervb) wrote :

Hi,

the release is pike 16.1.6, I do see the embedded details in the database. But we are still experiencing problems as we cannot resize the instance.
The flavor was recreated using the embedded details, but that did not help either, but at least we now have a flavor name iso a uuid.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
Changed in nova:
status: Expired → New
Revision history for this message
Matt Riedemann (mriedem) wrote :

You're saying that resize is failing on a server that is using a deleted flavor, but can you provide specific steps to recreate along with logs of the failure? I'm assuming these are the steps:

1. create server with flavor A
2. delete flavor A
3. resize server to flavor B

And you're saying #3 is failing but you're going to need to provide logs because I'm pretty sure we have functional tests for exactly this scenario to make sure it works.

Changed in nova:
status: New → Incomplete
Revision history for this message
Matt Riedemann (mriedem) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.