Bug 2132941 - floating ip quota usage doesn't reflect actual situation
Summary: floating ip quota usage doesn't reflect actual situation
Keywords:
Status: CLOSED DUPLICATE of bug 2102147
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.2 (Train)
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Rodolfo Alonso
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-07 09:14 UTC by Alex Stupnikov
Modified: 2022-10-11 08:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-11 08:10:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-19221 0 None None None 2022-10-07 09:27:03 UTC

Description Alex Stupnikov 2022-10-07 09:14:39 UTC
Description of problem:
Customer reported a problem in his RHOSP 16.2 deployment: from Neutron Server perspective there are 5 floating IPs used by specific project, but in reality there are no floating IPs in this project.

Problem was resolved when floating IP was created in affected project. More information about collected data will be provided privately.

This could be possibly related to bug #2130498, but symptoms are slightly different, so I am reporting separate bug.


Version-Release number of selected component (if applicable):
RHOSP 16.2.2


How reproducible:
$ openstack quota list --network --detail --project PROJ_ID -> tells that 5 floating IPs are used by customer

$ openstack floating ip list --project PROJ_ID  -> empty output

Comment 2 Rodolfo Alonso 2022-10-11 08:10:54 UTC
Hello Alex:

This is an issue on how the Neutron quota driver, using the new ``DbQuotaNoLockDriver`` class, retrieves the "quota --detail" (that is also used in the Horizon counters). This issue has been addressed in 16.2 [1] and will be ready in 16.2.4.

Regards.

[1]https://bugzilla.redhat.com/show_bug.cgi?id=2102147

*** This bug has been marked as a duplicate of bug 2102147 ***


Note You need to log in before you can comment on or make changes to this bug.