yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

The last check was done 1 year ago and this report describes multiple
issues at once. There is not enough time to double-check each bug
report. I'm closing this one. If you want to work on that, consider
opening new bug reports, each one with one single and very specific
issue. Otherwise it's not possible to solve them completely.

** Changed in: nova
       Status: Confirmed => Opinion

-- 
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/1083602

Title:
  Private flavors can't be used

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  I'm testing nova client 2.9.0.

  I worked as a user with admin privileges.

  I created a private flavor with command:

  $ nova flavor-create myFlavor 10 512 1 1 --is-public false
  +----+----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+
  | ID | Name     | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | extra_specs |
  +----+----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+
  | 10 | myFlavor | 512       | 1    | 0         |      | 1     | 1           | False     | {}          |
  +----+----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+

  Then, I associated the just created flavor to the tenant I was using
  with command:

  $ nova flavor-access-add 10 admin
  +-----------+-----------+
  | Flavor_ID | Tenant_ID |
  +-----------+-----------+
  | 10        | admin     |
  +-----------+-----------+

  If I list the flavors, with command nova flavor-list, the new flavor
  is not displayed:

  $ nova flavor-list
  +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+
  | ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | extra_specs |
  +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+
  | 1  | m1.tiny   | 512       | 0    | 0         |      | 1     | 1.0         | True      | {}          |
  | 2  | m1.small  | 2048      | 20   | 0         |      | 1     | 1.0         | True      | {}          |
  | 3  | m1.medium | 4096      | 40   | 0         |      | 2     | 1.0         | True      | {}          |
  | 4  | m1.large  | 8192      | 80   | 0         |      | 4     | 1.0         | True      | {}          |
  | 5  | m1.xlarge | 16384     | 160  | 0         |      | 8     | 1.0         | True      | {}          |
  +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+

  Even in the case I list with this other command, the new flavor is not
  shown:

  $ nova flavor-access-list --flavor=10
  ERROR: Failed to get access list for public flavor type.

  $ nova flavor-access-list --tenant admin
  ERROR: Sorry, query by tenant not supported.

  Please note that I get the same results if I don't associate the
  private flavor to any project.

  According to the specification I found here
  https://blueprints.launchpad.net/nova/+spec/project-specific-flavors,
  It seems to me that private flavor types are not working.

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