Red Hat Bugzilla – Bug 891302
Horizon doesn't display proper error when Quantum quota exceeded while creating networks
Last modified: 2016-04-26 09:53:09 EDT
Description of problem:
Horizon doesn't display proper error when Quantum quote exceeded
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.configure quantum to use quotes
( http://docs.openstack.org/folsom/openstack-network/admin/content/cfg_quotas_common.html )
2. configure amount of network to exceeded quote via horizon
3. check error output
Error by horizon : Failed to create
Error by CLI : "Quota exceeded for resources: ['network'] "
There is an upstream bug to try to make error messages relating to quotas more consistent across Horizon, this is another one to add to the list.
Although the upstream bug on making quotas more consistent in general hasn't been resolved yet, the error message for this particular quota is different on upstream master and more useful:
Error: Failed to create network "test": Quota exceeded for resources: ['network']
I'll see if it's possible and reasonable to extract and backport the change.
Issue still occurs in python-django-horizon-2012.2.3-8.el6ost.noarch
creating 10 subnets on the same network :
Error: Failed to create subnet 184.108.40.206/24, nothing about Quota
Thanks for the additional information Ofer. The initial bug report described an issue when creating new networks, which the patch focused on fixing. I agree the error handling should be more consistent though. Fixing this also for subnets can probably be done later in async in a separate bug, or if that's not acceptable I guess we can move this one out. I don't think it's a blocker. (For the record it's fixed in Grizzly.)
If the original issue is resolved, let's split the additional bug off.
ok, there is new bug for better error report
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.