he nova.quota_usages table frequently gets out-of-sync with the currently active/stopped instances in a tenant/project, specifically, there are times when the instance will be set to terminated/deleted in the instances table and the quota_usages table will retain the data, counting against the tenant's total quota. As far as I can tell there is no way to correlate instances.uuid with the records in nova.quota_usages. I propose adding an instance uuid column to make future cleanup of this table easier. I also propose a housecleaning task that does this clean up automatically.
Per launchpad bug discussion there is a blueprint addressing the core issue proposed here: https://blueprints.launchpad.net/nova/+spec/refresh-quotas-usage
********* VERSION ********* openstack-nova-api.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-cert.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-common.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-compute.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-conductor.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-console.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-novncproxy.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-scheduler.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost ********** LOGS ********** The feature was verified with automation https://review.gerrithub.io/#/q/project:RHOS-QE/RHOS-Tempest-Plugin Log files have been attached.
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://rhn.redhat.com/errata/RHEA-2016-2948.html