GBP doesn't respect Project quotas
Bug #1599218 reported by
venkat akkina
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
GBP doesn't respect project quotas and therefore, allows more security groups and networks to be created beyond what quotas have been set.
Revision history for this message
| Sumit Naiksatam (snaiksat) wrote | #1 |
| Changed in group-based-policy: | |
| status: | New → Incomplete |
To post a comment you must log in.
Can you please clarify if only the Neutron quotas are not being "respected" and if this is in regard to the implicitly created Neutron Security Groups and Neutron Networks? If so, this is expected and is not a bug. When using GBP API, there should not be any quota enforcement expectation for implicitly created Neutron resources.
As an aside, what release of GBP did you encounter this issue on?