Hide Forgot
Description of problem: Bug description from LP: ~~~ I have recently upgraded my cluster to Liberty for all projects. Now, when I create new instances, I frequently get an incorrect quota warning from the instance creation workflow, despite having plenty of available quota: "The requested instance cannot be launched as you only have 0 of your quota available." The issue is happening within the _get_tenant_compute_usages() check. That function determines (correctly) that I am able to list instances in all projects, so passes 'all_tenants' to the nova api. That results in an api call that looks like this: "GET /v2/<tenantid>/servers/detail?all_tenants=True&tenant_id=<tenantid> HTTP/1.1" Nova replies with a list of every instance in my entire cloud, 719 at last count. The call is very slow and, of course, 719 is many more than my instance quota for the current project, so Horizon determines that I am over quota. Note that this issue didn't appear when I was running Liberty Horizon with Kilo Nova (so maybe this is a bug or change in the nova-api) Best I can tell, the offending code in Horizon is still present in the git head. ~~~ Requested a patch(backport) to Liberty of LP#1610693 - https://bugs.launchpad.net/horizon/+bug/1610693 Version-Release number of selected component (if applicable): Red Hat OpenStack Platform 8
Customer applied https://review.openstack.org/#/c/422760 manually and works.
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Hi, it seems that the errata should be delivered on 2017-Mar-29 (custom), could you update to the BZ please.
I verified that the "launch instance" dialog now only shows the count of instances from the currently selected project, and not from all projects.
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/RHBA-2017:1471