Bug 1338699

Summary: page not found in nodes relationships
Product: Red Hat CloudForms Management Engine Reporter: Ronnie Rasouli <rrasouli>
Component: UI - OPSAssignee: Marek Aufart <maufart>
Status: CLOSED ERRATA QA Contact: Matouš Mojžíš <mmojzis>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: hkataria, jhardy, maufart, mmojzis, mpovolny, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.6.0.9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 16:05:10 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:
Embargoed:

Description Ronnie Rasouli 2016-05-23 09:42:54 UTC 
Description of problem:

Navigation failed "The page you were looking for doesn't exist." from relationships from nodes details
https://lynx03.qa.lab.tlv.redhat.com/ems_infra/show/888000000000001

Version-Release number of selected component (if applicable):
5.6.0.7-beta2.6-nightly.20160520110159_dde68fc 

How reproducible:

100%

Steps to Reproduce:
1.login to CFME 
2. go to compute --> infrastructure --> nodes
3. click on node thumbnail
4. click on Relationships --> Cloud/Infrastructure Providers: <provider name>

Actual results:

404 page https://lynx03.qa.lab.tlv.redhat.com/ems_infra/show/888000000000001

The page you were looking for doesn't exist.

You may have mistyped the address or the page may have moved.


Expected results:

go back to node list page

Additional info:
Comment 2 Marek Aufart 2016-05-23 11:41:14 UTC 
Fix https://github.com/ManageIQ/manageiq/pull/8888
Comment 3 Matouš Mojžíš 2016-06-02 12:05:31 UTC 
Verified in:5.6.0.9-rc2.20160531154046_b4e2f6d.
I was able to return from relationships of host(node) to provider.
Comment 5 errata-xmlrpc 2016-06-29 16:05:10 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