Author: yuntongjin <yuntong....@intel.com>
Date: Tue Mar 1 16:00:16 2016 +0800
Add members in InstanceGroup object members field
In InstanceGroup object, add_members method doesn't add members
into object members field, which causes
objects.Quotas.count(server_group_members) won't increase, and
instance group quota check invalid. This makes an issue that user
could spawn with one call more instances in server group than
was allowed in quota_server_group_members is it was below
instances quota settting.
Co-authored-by: yuntongjin <yuntong....@intel.com>
** Changed in: nova
Status: In Progress => Fix Released
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Quota_server_group_members parameter is not respected with
Status in OpenStack Compute (nova):
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.
nova boot --image $image --flavor small --hint
group=528ff1e3-5a6d-475c-826e-c70d7a56e769 --nic net-id=<UUID> --min-count=2
All Instances has spawned correct. In next request I have an error:
ERROR (Forbidden): Quota exceeded, too many servers in group (HTTP 403)
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
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
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp