Bug 1530575 - [UPSTREAM] Unexpected Error on Control > Explorer Screen
Summary: [UPSTREAM] Unexpected Error on Control > Explorer Screen
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Control
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: cfme-future
Assignee: Greg McCullough
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: 1526791
TreeView+ depends on / blocked
 
Reported: 2018-01-03 11:40 UTC by Guilherme Baufaker Rêgo
Modified: 2018-01-08 14:59 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-06 20:40:50 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screen Error (130.40 KB, image/png)
2018-01-03 11:40 UTC, Guilherme Baufaker Rêgo
no flags Details
Manageiq 1530575 (16.04 KB, text/plain)
2018-01-05 15:57 UTC, Guilherme Baufaker Rêgo
no flags Details

Description Guilherme Baufaker Rêgo 2018-01-03 11:40:51 UTC
Created attachment 1376299 [details]
Screen Error

Description of problem:

Navigating to Control > Explorer generates an unexpected error.

Version-Release number of selected component (if applicable):
Latest Manageiq Docker Image (Image ID: 7e1574071121)

How reproducible:

- Always

Steps to Reproduce:
1. Login on Manageiq
2. Navigate to Control
3. Click on Explorer


Actual results:

- Unexpected error on screen

Expected results:

Menus should appear (Policy Profiles, Policies, Conditions Events, Alerts, Alert Profile

Comment 5 Gregg Tanzillo 2018-01-04 21:29:52 UTC
Hi Guilherme, can you provide the log from this appliance so that we can see where the nil error is coming form? Thanks

Comment 6 Guilherme Baufaker Rêgo 2018-01-05 15:57:52 UTC
Created attachment 1377543 [details]
Manageiq 1530575

Comment 7 Greg McCullough 2018-01-05 17:55:58 UTC
Guilherme - This looks like it is related to configuration data stored in the advanced config section of the appliance.

Wondering if one or more of the following is possible?

1) Can we connect to the appliance experiencing this issue to review the configuration.

2) If not can we get an export of the database

3) You can also log into the appliance console and run the follow script using "bin/rails c" from the "/var/www/miq/vmdb" directory:

EmsEvent.event_groups.each do |_k, v|
  name = v[:name]
  puts "#{_k} #{v.inspect}\n\n" if v[:detail].nil?
end; nil

Comment 8 Guilherme Baufaker Rêgo 2018-01-05 23:21:30 UTC
Hi Greg,

I retested under "latest tag (image id: b68048004210)" and it seems to be working now and I can't reproduce the issue anymore

Comment 9 Greg McCullough 2018-01-06 20:40:50 UTC
Thanks, I'll close for now and we can reopen if needed.


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