yahoo-eng-team team mailing list archive

[Attila Fazekas <afazekas@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
         Status: New

** Attachment added: "quota-issue.sh"
   https://bugs.launchpad.net/bugs/1259524/+attachment/3926655/+files/quota-issue.sh

-- 
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/1259524

Title:
  Default security group is not calculated into the quata usage

Status in OpenStack Compute (Nova):
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1259524/+subscriptions