Created attachment 1215985 [details] CloudForms quota screenshot Description of problem: CloudForms displays an incorrect quota value for floating IPs for an OpenStack tenant. Version-Release number of selected component (if applicable): CFME 5.6.2.2.20161017185613_7cee0a0 openstack-neutron v7.0.4 r11.el7ost (RHOSP 8, deployed via PackStack) openstack-nova-common v12.0.4 r4.el7ost (RHOSP 8, deployed via PackStack) How reproducible: 100% Steps to Reproduce: 1. Login to OpenStack as an admin user 2. Select "Identity" -> "Projects", and "Create Project" 3. Specify a name, and add the admin user as a member to the project 4. Select the "Quota" tab, and enter the floating IPs quota as 50 5. Select "Create Project" 6. Login to CloudForms as the admin user, and select "Compute" -> "Clouds" -> "Providers" 7. Select the OpenStack provider, and select "Configuration" -> "Refresh Relationships and Power States" 8. Once the provider has refreshed, select "Cloud Tenants", and select the newly created tenant. Actual results: CloudForms displays the tenant floating IP quota as "0 used of 10" Expected results: CloudForms displays the tenant floating IP quota as "0 used of 50"
Created attachment 1215998 [details] OpenStack project quota
Please assess the importance of this issue and update the priority accordingly. Somewhere it was missed in the bug triage process. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#priority for a reminder on each priority's definition. If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.
Quotas from Neutron were not being collected correctly, so the floating IP quota that was being displayed was from the Compute service. This PR should cause the Networking quotas to be collected correctly. https://github.com/ManageIQ/manageiq-providers-openstack/pull/272
Verified on 5.10.0.2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212