← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1262595] [NEW] getting flavor by id prefers deleted flavors

 

Public bug reported:

After changing my m1.tiny flavor from disk_gb==1 to disk_gb==0 I noticed
something strange:

$ nova flavor-list
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
| 1  | m1.tiny   | 512       | 0    | 0         |      | 1     | 1.0         | True      |

Here the correct flavor is being shown. however when looking at it with
details:

$ nova flavor-show 1

+----------------------------+---------+
| Property                   | Value   |
+----------------------------+---------+
| name                       | m1.tiny |
| ram                        | 512     |
| OS-FLV-DISABLED:disabled   | False   |
| vcpus                      | 1       |
| extra_specs                | {}      |
| swap                       |         |
| os-flavor-access:is_public | True    |
| rxtx_factor                | 1.0     |
| OS-FLV-EXT-DATA:ephemeral  | 0       |
| disk                       | 1       |
| id                         | 1       |
+----------------------------+---------+


disk_gb (here shown as "disk" is shown as 1. This is because the database query simply returns .first() match, which in my case is returning the deleted instance_type.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  getting flavor by id prefers deleted flavors

Status in OpenStack Compute (Nova):
  New

Bug description:
  After changing my m1.tiny flavor from disk_gb==1 to disk_gb==0 I
  noticed something strange:

  $ nova flavor-list
  +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
  | ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
  +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
  | 1  | m1.tiny   | 512       | 0    | 0         |      | 1     | 1.0         | True      |

  Here the correct flavor is being shown. however when looking at it
  with details:

  $ nova flavor-show 1

  +----------------------------+---------+
  | Property                   | Value   |
  +----------------------------+---------+
  | name                       | m1.tiny |
  | ram                        | 512     |
  | OS-FLV-DISABLED:disabled   | False   |
  | vcpus                      | 1       |
  | extra_specs                | {}      |
  | swap                       |         |
  | os-flavor-access:is_public | True    |
  | rxtx_factor                | 1.0     |
  | OS-FLV-EXT-DATA:ephemeral  | 0       |
  | disk                       | 1       |
  | id                         | 1       |
  +----------------------------+---------+

  
  disk_gb (here shown as "disk" is shown as 1. This is because the database query simply returns .first() match, which in my case is returning the deleted instance_type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1262595/+subscriptions


Follow ups

References