Red Hat Bugzilla – Bug 1412684
Issue with fog-openstack 'update_quota.rb'
Last modified: 2017-08-29 23:49:52 EDT
New commit detected on ManageIQ/manageiq/darga: https://github.com/ManageIQ/manageiq/commit/a6c651f4b7e5cf540af0276dd9571bec8b2f6aac commit a6c651f4b7e5cf540af0276dd9571bec8b2f6aac Author: Satoe Imaishi <simaishi@redhat.com> AuthorDate: Thu Jan 12 09:42:43 2017 -0500 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Mon Jan 30 10:07:51 2017 -0500 Merge pull request #13417 from sseago/tenant-id-quota-set [EUWE] Upgrade fog-openstack to 0.1.19 (cherry picked from commit 01d4d851f829c8670d4b2561114ba10ad4dff96b) https://bugzilla.redhat.com/show_bug.cgi?id=1412684 gems/pending/Gemfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
The backport PR is merged.
There is no tenant CRUD in CFME 5.6.4.0
AFAIK this has nothing to do with tenant CRUD. Scott, can you give an example of how to access this functionality?
This bug was originally reported in 5.6. I never got a response from the original reporter as to exactly how they hit the bug originally. I was able to reproduce it by invoking the reported fog-openstack API commands directly in the rails console, since I was never able to figure out how to hit the bug via the Web UI. So you probably have 2 options: 1) Find out from sacpatil@redhat.com how the bug was originally discovered and verify it the same way 2) verify by manually running fog-openstack update quota API calls.
Please provide steps to reproduce, in 5.6 there isn't a method to create new tenants, please explain in details how did they create the tenants. by openstack CLI? since the options does not exist on UI
Hello Scott, > Find out how the bug was originally discovered and verify it the same way CU never disclosed how they called update_quote() I can only guess that it was called using automate method. If need I can ask CU. > verify by manually running fog-openstack update quota API calls. Running update_quota API calls should be a good test
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/RHBA-2017-0474.html