Bug 1330767

Summary: 'The page you were looking for doesn't exist' error while clicking provider link from event bubble
Product: Red Hat CloudForms Management Engine Reporter: Nandini Chandra <nachandr>
Component: UI - OPSAssignee: Aparna Karve <akarve>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: timelines
Fixed In Version: 5.6.0.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 15:55:12 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-26 22:25:33 UTC 
Description of problem:
------------------------


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


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


Steps to Reproduce:
-------------------
1.Manage a provider.Generate an event for a VM (Eg:Power off a VM.Tested this with vsphere). 
2.From the VM summary page, click Monitoring, then click Timelines.
3.Click the event for the event bubble to pop up.In the event bubble, click the provider link.


Actual results:
--------------
'The page you were looking for doesn't exist' error


Expected results:
-----------------
No errors


Additional info:
----------------
Comment 3 Aparna Karve 2016-04-28 23:40:14 UTC 
Nandini,

This should be fixed in the next build.

Thanks,
Aparna
Comment 4 Nandini Chandra 2016-05-04 16:59:49 UTC 
Verified in  5.6.0.5.
Comment 6 errata-xmlrpc 2016-06-29 15:55:12 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