Description of problem: When logging into horizon, horizon sends an API request to nova inquiring about usage statistics. Among the api requests is os-simple-tenant-usage. We see that, if there are thousands of deleted VMs in the nova DB, this api call makes the nova-api process memory consumption skyrocket. If there are enough deleted VMs in the DB the nova-api eventually crashes due to lack of memory. I was able to reproduce this in a lab setup (by running a script that creates many VMs and then deletes them continuously). I was also able to make the problem go away by deleting the VM entries from the nova database. Version-Release number of selected component (if applicable): OSP6 Proposed fix - https://review.openstack.org/#/c/201221/ ~~~ Add an OPENSTACK_SIMPLE_TENANT_USAGE_ENABLED settings option The users may want to disable the simple tenant usage display for efficiency reasons -- currently this gets very slow and may run out of memory if there are a lot of deleted machines in the Nova database. In the 2.0 API we can disable it on the Nova side, but it won't be possible anymore with the 2.1 API. ~~~ Additional info: related to BZ1154237
We came up with a more generic solution: ~~~ Add OPENSTACK_NOVA_EXTENSIONS_BLACKLIST option to settings This lets us disable any Nova extension we like, not just the simple tenant usage. ~~~
The patch has been merged upstream.
Verified ======== openstack-dashboard-2014.2.3-6.1.el7ost.noarch python-django-horizon-2014.2.3-6.1.el7ost.noarch
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/RHSA-2015-1679.html