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 1361844

Summary: Relationship links lead to wrong menu in OSE project
Product: Red Hat CloudForms Management Engine Reporter: Pavel Zagalsky <pzagalsk>
Component: UI - OPSAssignee: Harpreet Kataria <hkataria>
Status: CLOSED ERRATA QA Contact: Einat Pacifici <epacific>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: cpelland, dajohnso, dclarizi, efreiber, fsimonce, hkataria, jhardy, jprause, juwatts, mpovolny, obarenbo, sbulage
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.1Flags: epacific: automate_bug-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: container
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-18 18:00:36 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 Pavel Zagalsky 2016-07-31 08:01:19 UTC
Description of problem:
If you go to an OpenShift project and click Relationships all the links point to the same menu that shows all the projects

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

How reproducible:
Every time

Steps to Reproduce:
1. In CF UI, click Compute -> Container -> Projects
2. Select a project
3. Click the Relationships Accordion 
4. Click any of the links (such as container provider, routes, services, etc)

Actual results:
Each link will bring the user to the projects menu

Expected results:
Pressing the link should lead to the corresponding menu. ie: pods link should bring up the pods menu

Additional info:

Comment 2 Erez Freiberger 2016-07-31 12:13:37 UTC
This bug is only present on the Darga branch and not no the master branch so this bug's target version should be changed to 5.6.1

Comment 3 Erez Freiberger 2016-07-31 13:15:17 UTC
This PR fixed it but for some reason it was set as "darga/no":

Comment 5 Federico Simoncelli 2016-08-02 09:38:00 UTC
Shouldn't this be on POST?

Comment 6 Harpreet Kataria 2016-08-02 13:23:22 UTC
PR has been backported to Darga, sending this to POST.

Comment 8 Harpreet Kataria 2016-08-02 17:48:46 UTC
PR against Darga:

Comment 9 CFME Bot 2016-08-03 21:45:42 UTC
New commit detected on ManageIQ/manageiq/darga:

commit 7a42fce219a2e5c7dffdfaa5683a15e7b2fabaec
Author:     Harpreet Kataria <>
AuthorDate: Tue Aug 2 13:44:38 2016 -0400
Commit:     Harpreet Kataria <>
CommitDate: Tue Aug 2 13:44:38 2016 -0400

    Fix Relationship links for a Middleware Provider
    The Middleware Provider controller (ems_middleware) does not support RESTful routing yet, therefore the Relationship links should be routed using :controller, :action and :id
    cherry-picking changes from
    Fixes #8803

 app/helpers/application_helper.rb       | 15 ++++++++++++---
 spec/helpers/application_helper_spec.rb | 10 ++++++++++
 2 files changed, 22 insertions(+), 3 deletions(-)

Comment 12 errata-xmlrpc 2016-08-18 18:00:36 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.