Quotas updates in Horizon are validated against current user project usage (rather than targetted project's usage)

[Anurag Ramu]

Admin project has 10 VMs spawned and project "test" has none. When logged in as 'admin', attempt to set "test" project quota to any value less than 10 under instances section, results in failure because quotas cannot be set to a value that is lower than current used resources.
This issue is producible in Newton, Ocata and Pike.

[Gao Fei (gaofei-inspur)]

this bug has been corrected in master
https://github.com/openstack/horizon/commit/33dc94079cc25128998d2f339e664a775ce82396#diff-7fe1dd68aabf299a5b256447eccc5678

[Anurag Ramu (anuragr1995)]

I've tried with these changes already but it doesn't work. Are there any other changes required apart from these changes in quotas.py files under usage and tests directories?

[Akihiro Motoki (amotoki)]

I cannot reproduce the issue after the corresponding patch was backported to stable/pike.
https://review.openstack.org/#/c/534348/

I believe this is a duplicate of bug 1713724

[Launchpad Janitor (janitor)]

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]