Red Hat Bugzilla – Bug 1511682
Quota error when adding a group to a Project using Horizon
Last modified: 2018-06-27 09:39:48 EDT
Created attachment 1350110 [details] Horizon error screenshot Description of problem: Using Horizon, customer encounters the following quota error. However, doing the same thing through the CLI succeeds. Version-Release number of selected component (if applicable): RHOSP9 How reproducible: 100% Actual results: Project is not adding, with erroneous quota error as attached in screenshot. Expected results: Project is added successfully. Additional info: As stated, there is no problem through CLI, so this looks like Horizon only.
Based on the logs, is the cause of this the same as https://bugzilla.redhat.com/show_bug.cgi?id=1522705 ? If so we will fix it there and close as duplicate, if not, please provide the CLI logs so that we can compare what quotas are being shown.
@Beth The error msg is indeed the same (differs only in values), however it's hit when adding a group to a project not simply altering the quota as in the other bug. Not sure I would put it all in the same pile. As to which cli logs do you require? Something like bellow? ~~~ source admin.rc openstack role add --debug --group $g_uuid --project $p_uuid user ~~~ * I have requested this from the cu in pre-emption. Also note that the CLI commands does succeed. Cheers, -Marc
It would be interesting to see the quotas for the project being modified and for the user's default project — as displayed by the CLI and as displayed by Horizon.
After looking at the code, I can only find one place where this error message is used, and it is now fixed in Queens by https://review.openstack.org/510188
This is now fixed by the linked review and I can confirm this error is fixed.
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/RHEA-2018:2086