Bug 1470309 - API request for VM information failing
API request for VM information failing
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: GA
: cfme-future
Assigned To: Gregg Tanzillo
Dave Johnson
Depends On:
  Show dependency treegraph
Reported: 2017-07-12 13:28 EDT by Chris Hale
Modified: 2017-12-05 10:15 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-14 14:39:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Hale 2017-07-12 13:28:53 EDT
Description of problem:
When attempting to make a request details on a VM we are receiving the following error. 
Looked at the log, and seeing an API error:

    "error": {
        "kind": "internal_server_error",
        "message": "undefined method `keys' for nil:NilClass",
        "klass": "NoMethodError"

From this URL:


Additional info:
We make this request in the SUI on the VM details page.
Comment 2 Chris Hale 2017-07-12 13:31:00 EDT
Actually , we make this request from the Service details page not the VM details page.
Comment 3 Dave Johnson 2017-07-13 23:01:03 EDT
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.
Comment 4 Jillian Tullo 2017-07-14 14:39:04 EDT
Marking this as notabug.

After discussing with Chris and recreating locally, it is an issue with the same sample database that we are using (this is an issue that has only been seen locally). Some of the orchestration stack resources were removed (most likely for sanitation purposes) but their references remain, which results in orchestration_stacks returning [nil].

In real life this would not happen because the references would be removed (have ensured the relationship is configured properly).

Note You need to log in before you can comment on or make changes to this bug.