Bug 1394850

Summary: Topology - error page clicking on any non-provider entity
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: UI - OPSAssignee: Andrey <aveselov>
Status: CLOSED ERRATA QA Contact: Satyajit Bulage <sbulage>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: cpelland, hkataria, jhardy, mhradil, mpovolny, obarenbo, sbulage, tzumainn
Target Milestone: GA   
Target Release: 5.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.7.0.11 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1394733 Environment:
Last Closed: 2017-01-04 13:13:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1394733    
Bug Blocks:    

Comment 2 CFME Bot 2016-11-14 15:11:12 UTC 
New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/16e04748068b367a24fc53809d660217db06372b

commit 16e04748068b367a24fc53809d660217db06372b
Author:     Martin Hradil <himdel>
AuthorDate: Mon Nov 14 16:28:55 2016 +0200
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Mon Nov 14 10:09:19 2016 -0500

    Merge pull request #12607 from andyvesel/fix_wrong_url_when_clicking_entities_on_topology_page
    
    Fix wrong urls when clicking entity on topology page
    (cherry picked from commit 582d95a0124ec4d6ab6807ae1a99c19c6ac7d9f8)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1394850

 app/assets/javascripts/services/topology_service.js | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
Comment 3 Satyajit Bulage 2016-11-16 09:22:53 UTC 
After clicking on non-provider entity like Floating IP, showing right details and URL = /floating_ip/show/11.

Verified Version:- 5.7.0.11-rc1.20161115160629_46cf4f1
Comment 5 errata-xmlrpc 2017-01-04 13:13:07 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://rhn.redhat.com/errata/RHBA-2017-0012.html