openstack limits --absolute show wrong count for security groups

Bug #1632460 reported by Sivasathurappan Radhakrishnan
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
python-openstackclient
New
Undecided
Sivasathurappan Radhakrishnan

Bug Description

OpenStack limits --absolute shows wrong count for 'totalSecurityGroupsUsed'. Despite creating multiple security groups still, the count shows as 1.

openstack security group create <name> uses neutron API to create security group
openstack limits show --absolute fetches the information from nova api. Since nova-network has been deprecated and current devstack installation runs with neutron as default, it's better to change the way how how openstack limits show fetches its information

Tags: network
Changed in python-openstackclient:
assignee: nobody → Sivasathurappan Radhakrishnan (siva-radhakrishnan)
Richard Theis (rtheis)
tags: added: network
Revision history for this message
Ankur (ankur-gupta-f) wrote :

No such current way to retrieve this information from the Neutron API. Discussions on going

Revision history for this message
tom king (kingttx) wrote :

As of python-openstackclient 3.13.0, this is still an issue.

Revision history for this message
tom king (kingttx) wrote :

From a related bug in nova client:
https://bugs.launchpad.net/python-novaclient/+bug/1731323/comments/4

"The security_group quota and usage in nova is only related to security groups created with nova-network. When using neutron, the quotas and usage are handled by neutron, not nova."

I've pasted Ankur's comment into their ticket.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.