Bug 1711231

Summary: Getting error "undefined method `>' for nil:NilClass [vm_cloud/explorer]" while accessing cloudforms instance
Product: Red Hat CloudForms Management Engine Reporter: Nikhil Gupta <ngupta>
Component: ProvidersAssignee: Adam Grare <agrare>
Status: CLOSED DUPLICATE QA Contact: Omri Hochman <ohochman>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.9.9CC: jfrey, jhardy, jprause, mshriver, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-20 07:13:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Error screenshot none

Description Nikhil Gupta 2019-05-17 09:48:36 UTC
Created attachment 1569991 [details]
Error screenshot

Description of problem:
Cannot see content on cfme instance running on OpenStack provider.

Version-Release number of selected component (if applicable):
OpenStack 10
cfme-5.9

How reproducible:
Alwasy

Steps to Reproduce:
1. Run an cfme instance without flavor on OSP10
2. Add OSP10 provider to CF
3. Go to Compute -> Clouds -> Tenants -> Click on tenant -> Click on Instances
4. Then click on 'cfme' instance

Actual results:
~~~
Unexpected error encountered
Error text:
undefined method `>' for nil:NilClass [vm_cloud/explorer]
~~~

Expected results:
Should be able to access instance details.

Comment 3 Adam Grare 2019-05-17 11:25:36 UTC
This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1624535
What version exactly is the customer on?

Comment 4 Nikhil Gupta 2019-05-20 07:13:36 UTC
It cfme-5.9.4. After updating the cloudforms to latest version i.e. 5.9.9, I am not seeing this issue.

Thank you Adam.

*** This bug has been marked as a duplicate of bug 1624535 ***