It actually looks like this is a limitation in the flavors API in nova, you can't filter on name:
https://github.com/openstack/nova/blob/347ebb20e3217c2f8abf261622ba420c9fd077bd/nova/api/openstack/compute/flavors.py#L78 We'd have to update the API to do this, and at least for this case it's probably not going to happen, since most deployments probably don't have 1000+ flavors to pick from. ** Changed in: nova Importance: Medium => Low ** Tags added: api ** Changed in: nova Status: Triaged => Won't Fix ** Changed in: nova Importance: Low => Undecided -- 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/1567114 Title: nova boot specifying flavor by name fails intermittently past 1000 flavors Status in OpenStack Compute (nova): Won't Fix Bug description: While running a script which: 1) creates a project 2) creates a user in that project 3) creates a flavor 4) tweaks some nova and neutron quotas for that project 5) switches to that project 6) creates an image 7) tweaks some security group rules 8) creates a network/subnet/router tuple 9) creates a port 10) creates a floating IP with that port id and finally 11) nova boots with that port, image (by name) and flavor (again by name) once one gets above 1000 iterations, the nova boot will start to fail from time to time with messages like: ERROR (CommandError): No flavor with a name or ID of 'uberplay1053' exists. It isn't every nova boot past the 1000th flavor: ERROR (CommandError): No flavor with a name or ID of 'uberplay1053' exists. ERROR (CommandError): No flavor with a name or ID of 'uberplay1055' exists. ERROR (CommandError): No flavor with a name or ID of 'uberplay1062' exists. ERROR (CommandError): No flavor with a name or ID of 'uberplay1064' exists. ... ERROR (CommandError): No flavor with a name or ID of 'uberplay1312' exists. ERROR (CommandError): No flavor with a name or ID of 'uberplay1316' exists. ERROR (CommandError): No flavor with a name or ID of 'uberplay1319' exists. ERROR (CommandError): No flavor with a name or ID of 'uberplay1321' exists. The "holes" in that sequence are good - those instances booted and were accessible just fine. The flavors themselves are there - they can be seen via nova flavor-show <UUID>. This is with Liberty. There were 6 flavors already defined before the script was started. "uberplay1053" was the first failure, counting in that sequence started at 0. I will (attempt to) attach the script shortly. ~/rjones2$ nova --version 2.30.3 Neutron networking with OVS. Instances using local storage not Cinder. Glance using Swift for image storage. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1567114/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
