Bug 1330230

Summary: 'The page you were looking for doesn't exist' error while viewing provider timelines
Product: Red Hat CloudForms Management Engine Reporter: Nandini Chandra <nachandr>
Component: UI - OPSAssignee: Zita Nemeckova <znemecko>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: akarve, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.6.0.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 15:54:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nandini Chandra 2016-04-25 16:45:37 UTC 
Description of problem:
------------------------


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


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.Navigate to the summary page of a provider.
2.Click 'Monitoring', click 'Timelines'.


Actual results:
--------------
'The page you were looking for doesn't exist' error while viewing provider timelines.


Expected results:
-----------------
The timelines page should be displayed.


Additional info:
---------------
Comment 2 Nandini Chandra 2016-04-25 16:48:08 UTC 
The events are present in the event_streams table.I've seen this issue happen with both RHEV and vSphere.I'll test cloud providers and update the BZ.
Comment 3 Aparna Karve 2016-04-26 16:01:46 UTC 
PR - https://github.com/ManageIQ/manageiq/pull/8222
Comment 4 Nandini Chandra 2016-05-04 16:53:55 UTC 
Verified in 5.6.0.5
Comment 6 errata-xmlrpc 2016-06-29 15:54:21 UTC 
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://access.redhat.com/errata/RHBA-2016:1348