Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696697 - Unexpected error when viewing request details
Summary: Unexpected error when viewing request details
Keywords:
Status: ON_DEV
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.10.4
Assignee: Harpreet Kataria
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-05 12:49 UTC by Ryan Spagnola
Modified: 2019-04-16 12:08 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)

Description Ryan Spagnola 2019-04-05 12:49:21 UTC
Description of problem:
When clicking on a request to view details an unexpected error occurs.

Version-Release number of selected component (if applicable):
5.9.9

How reproducible:


Steps to Reproduce:
1. Go to Services > Requests
2. Click on a request

Actual results:
Unexpected Error

undefined method `[]' for nil:NilClass [miq_request/show]

Expected results:
Request details displayed

Additional info:
Also seen in 5.9.8

Comment 7 William Fitzgerald 2019-04-09 19:51:01 UTC
Ryan,

When I open up the request in the UI, it is running the dialogs.  The dialogs have an error and this causing the UI to fail.
We believe this issue has been addressed here :

https://bugzilla.redhat.com/show_bug.cgi?id=1667948

Can you test on version 5.9.8.0.20190121201402_b1df4c2 or later ?

Thanks

Billy

Comment 8 Ryan Spagnola 2019-04-09 20:37:47 UTC
Billy,

The first reproducer is on 5.9.9.


Thanks, 
Ryan


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