limits API isn't filtering security groups and floating IPs from 2.36 response
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Unassigned |
Bug Description
The limits API isn't filtering out network resources like security groups and floating IPs from the 2.36 response (like it does for quota sets):
I found this when testing some changes in novaclient for 2.36.
DEBUG (session:337) REQ: curl -g -i -X GET http://
DEBUG (connectionpool
DEBUG (session:366) RESP: [200] Content-Length: 430 Content-Type: application/json Openstack-
RESP BODY: {"limits": {"rate": [], "absolute": {"maxServerMeta": 128, "maxPersonality": 5, "totalServerGro
Changed in nova: | |
milestone: | none → newton-3 |
Reviewed: https:/ /review. openstack. org/356694 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=4461cdf4c46 4ecf54444c8d865 44453f30de1fd4
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4461cdf4c464ecf 54444c8d8654445 3f30de1fd4
Author: Sean Dague <email address hidden>
Date: Wed Aug 17 16:20:45 2016 -0400
don't report network limits after 2.35
We correctly stopped reporting the limits for things like security
groups and floating ips after mv 2.35. We completely missed that
limits are modified by the used_limits extension, and hilarity
ensued. We were reporting no maxSecurityGroups over the wire, but we
were reporting totalSecurityGroups through the magic of extensions.
Change-Id: I85b2b41d919ed6 987d4c9288905cc ce49c10c81f
Closes-Bug: #1614133