Juno is EOL [1] so we aren't doing fixes for it anymore. I've closed this as invalid, but if you still have this issue in a later, supported release, please feel free to reopen this issue and provide the updated version details of your environment in the description.
References: -------------- [1] http://docs.openstack.org/releases/ ** Changed in: nova Status: New => Invalid -- 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/1538169 Title: Quota_server_group_members parameter is not respected by nova Status in OpenStack Compute (nova): Invalid Bug description: When I create instances which I want to be in the same server group (--hint group=<UUID>) with parameter: --num-instances or --min-count /--max-count and I have quota_server_group_members set to 5, nova is spawning all instances regardless quota. Example: nova boot --image $image --flavor small --hint group=528ff1e3-5a6d-475c-826e-c70d7a56e769 --nic net-id=<UUID> --min-count=2 --max-count=10 test-instance All Instances has spawned correct. In next request I have an error: ERROR (Forbidden): Quota exceeded, too many servers in group (HTTP 403) (Request-ID: req-f8aa39cd-2a14-486d-95a9-747ed9eecbfc) Normally request which should spawn 10 instances (but quota is set to 5) should give an error with Quota exceeded. The same situation is with --num-instances parameter. I check it many times in Juno release and on devstack using nova master branch. I added simple patch to forbidden creating new instances over quota, but it's should be changed and it's not working correctly with --min-count/--max-count parameter. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1538169/+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
