yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1152548@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

Hi,
we're running Folsom on CentOS.

When playing with instance types it seems that the flavor IDs get reused
when a flavor is deleted. Here's a copy paste from the instance_types
table from the nova database.

| created_at          | updated_at | deleted_at          | deleted | name                  | id | memory_mb | vcpus | swap | vcpu_weight | flavorid | rxtx_factor | root_gb | ephemeral_gb | disabled | is_public |
| 2013-02-28 10:24:05 | NULL       | 2013-02-28 11:37:49 |       1 | m1.fullnode-smalldisk | 18 |    440000 |    24 |    0 |        NULL | 7        |           1 |      50 |          150 |        0 |         1 |
| 2013-02-28 11:37:49 | NULL       | NULL                |       0 | m1.fullnode-smalldisk | 19 |    440000 |    24 |    0 |        NULL | 7        |           1 |      10 |          150 |        0 |         1 

Here I added a fullnode-smalldisk flavor, then noticed I did it wrong,
deleted it, and created a new one. You see that the flavor id is 7 on
both flavors, and one is marked deleted. I did these flavor changes over
from horizon, but I assume it uses the same API independent of the
client.

One problem is that this makes it much harder to correlate historical
data. However, the bigger problem is that if I launch one of these, I
get a VM with the specs of the deleted flavor. So there is a bug
somewhere else too (when launching machines, deleted flavors are also
used) , but for clarity, I think the flavorids should not be reused at
all.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
Flavor IDs of deleted flavors get reused
https://bugs.launchpad.net/bugs/1152548
You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).