Default security group is not calculated into the quata usage

[Attila Fazekas]

Whit a tenant where the 'default' security group not yet implicitly created , sever thing behaves differently.

- When the security group quota limit is 10 and the user creates 10 security groups before listing the security groups or booting a vm, he will have 11 security group after list or boot.

- Before the security groups listed the the maximum quota can be set to 0, but after the listing it will be rejected by,
'Quota value 0 for security_groups are less than already used and reserved 1 '

Please see the attached shell script for details about how to reproduce the issue.

With
WORKING=part quota-issue.sh # everything behaves like the 'default' quota is part of the quota.
with
WORKING=not_part quota-issue.sh the tested situations behaves like the default quota is not part of the quota usage.

[Abhishek Talwar (abhishek-talwar)]

Hey,

I tried to replicate this bug but i don't think the same issue exists now. With one security group already being there, tried to create 10 more security groups but it gives error when you are creating the 10th security group ( 1 default group and 9 more created) :
Quota exceeded, too many security groups. (HTTP 413) (Request-ID: req-190bd0a4-30b9-4b2d-8921-aeee9c64eca4)