Public bug reported:
Setup credentials to allow access to Nova as an administrator account
[root@localhost ] # . keystonerc_admin
[root@localhost ~(keystone_admin)]#
Now create a new flavor but mark it as non-public
[root@localhost ~(keystone_admin)] # nova flavor-create --is-public False
astrochicken 21 2048 20 1
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor
| Is_Public |
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
| 21 | astrochicken | 2048 | 20 | 0 | | 1 | 1.0
| False |
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
Then try a boot an instance using this flavour, specified by name
[root@localhost ~(keystone_admin)] # nova boot --flavor astrochicken vmm
ERROR: No flavor with a name or ID of 'astrochicken' exists.
This is clearly bogus as we just created the flavor successfully.
Booting the instance succeeds with specifying the flavor ID instead of
its name. So whatever resolves flavor names is failing for the non-
public flavor, even when the user has permission to see the non-public
flavor.
It is also noted that the flavour does not appear in the listing by
default
[root@localhost ~(keystone_admin)]# nova flavor-list
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor |
Is_Public |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
| 1 | m1.tiny | 512 | 1 | 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 |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
[root@localhost ~(keystone_admin)]# nova flavor-list --all
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor
| Is_Public |
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
| 1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0
| True |
| 2 | m1.small | 2048 | 20 | 0 | | 1 | 1.0
| True |
| 21 | astrochicken | 2048 | 20 | 0 | | 1 | 1.0
| False |
| 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 |
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
** 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/1327212
Title:
Instances cannot be booted using name of a non-public, but accessible,
flavor
Status in OpenStack Compute (Nova):
New
Bug description:
Setup credentials to allow access to Nova as an administrator account
[root@localhost ] # . keystonerc_admin
[root@localhost ~(keystone_admin)]#
Now create a new flavor but mark it as non-public
[root@localhost ~(keystone_admin)] # nova flavor-create --is-public False
astrochicken 21 2048 20 1
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs |
RXTX_Factor | Is_Public |
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
| 21 | astrochicken | 2048 | 20 | 0 | | 1 | 1.0
| False |
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
Then try a boot an instance using this flavour, specified by name
[root@localhost ~(keystone_admin)] # nova boot --flavor astrochicken vmm
ERROR: No flavor with a name or ID of 'astrochicken' exists.
This is clearly bogus as we just created the flavor successfully.
Booting the instance succeeds with specifying the flavor ID instead of
its name. So whatever resolves flavor names is failing for the non-
public flavor, even when the user has permission to see the non-public
flavor.
It is also noted that the flavour does not appear in the listing by
default
[root@localhost ~(keystone_admin)]# nova flavor-list
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor
| Is_Public |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
| 1 | m1.tiny | 512 | 1 | 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 |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
[root@localhost ~(keystone_admin)]# nova flavor-list --all
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs |
RXTX_Factor | Is_Public |
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
| 1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0
| True |
| 2 | m1.small | 2048 | 20 | 0 | | 1 | 1.0
| True |
| 21 | astrochicken | 2048 | 20 | 0 | | 1 | 1.0
| False |
| 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 |
+----+--------------+-----------+------+-----------+------+-------+-------------+-----------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1327212/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
