Description of problem: Cloudforms is unable to collect inventory for a openstack environment that has ~7 missing instances. [----] E, [2014-11-17T21:55:10.478421 #25433:924014] ERROR -- : excon.error #<Excon::Errors::Unauthorized: Expected([200, 204]) <=> Actual(401 Unauthorized) response => #<Excon::Response:0x00000007194cc0 @data={:body=>"{\"error\": {\"message\": \"The request you have made requires authentication.\", \"code\": 401, \"title\": \"Unauthorized\"}}", :headers=>{"Vary"=>"X-Auth-Token", "Content-Type"=>"application/json", "Conte nt-Length"=>"114", "Date"=>"Mon, 17 Nov 2014 21:55:26 GMT"}, :status=>401, :remote_ip=>"10.63.29.248"}, @body="{\"error\": {\"message\": \"The request you have made requires authentication.\", \"code\": 401, \"title\": \"Unauthorized\"}}", @headers={"Vary"=>"X-Auth-Toke n", "Content-Type"=>"application/json", "Content-Length"=>"114", "Date"=>"Mon, 17 Nov 2014 21:55:26 GMT"}, @status=401, @remote_ip="10.63.29.248">> Version-Release number of selected component (if applicable): 5.3.0 How reproducible: n/a Steps to Reproduce: 1. n/a 2. 3. Actual results: Expected results: Additional info:
Fix is in this upstream patch: https://github.com/ManageIQ/manageiq/commit/22bccfcd2cd2cc1e3a5bc383329b1ba9972e245f Need to separate out the changes in #parse_volume and patch in 5.3.z.
New commit detected on cfme/5.3.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=7c94e2ec66d92751e96646092fa4b2e30debdaf6 commit 7c94e2ec66d92751e96646092fa4b2e30debdaf6 Author: Greg Blomquist <gblomqui> AuthorDate: Thu Dec 4 15:58:46 2014 -0500 Commit: Greg Blomquist <gblomqui> CommitDate: Thu Dec 4 16:32:36 2014 -0500 Handle openstack inventory case where volume not accessible There can be cases in Openstack Inventory collection when a volume that's attached to an instance is not visible in the tenants associated with the OpenStack user account. In this case, trying to dereference the data causes a Nil Reference error. Now, the code will simply log that it cannot access the volume and leave the volume's inventory data uncollected and the linkage to the instance unset. This was fixed upstream as part of PR 681. https://github.com/ManageIQ/manageiq/pull/681 The original upstream patch can be found in commit: 22bccf https://github.com/ManageIQ/manageiq/commit/22bccf https://bugzilla.redhat.com/show_bug.cgi?id=1165305 vmdb/app/models/ems_refresh/parsers/openstack.rb | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-)
*** Bug 1166282 has been marked as a duplicate of this bug. ***
*** Bug 1166295 has been marked as a duplicate of this bug. ***
Josh, can you take a crack at explaining how the customer got into the state of having instances in one tenant and volumes in another? My guess is that they associated the volumes to the instances, and then later moved the volumes or instances to another tenant. In fact, I sort of remember something about this case where the customer was moving instances around, maybe?
Unable to reproduce this issue. Customer(from case # 01284590) has verified that the fix provided fixes the issue in their setup.Marking the BZ as verified.
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/RHSA-2015-0028.html