Bug 1436226

Summary:	Persistent volume relationship link broken
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	Providers	Assignee:	zakiva
Status:	CLOSED ERRATA	QA Contact:	Einat Pacifici <epacific>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.8.0	CC:	cpelland, epacific, fsimonce, jfrey, jhardy, obarenbo, simaishi
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.3
Hardware:	x86_64
OS:	Linux
Whiteboard:	container:ui
Fixed In Version:	5.7.3.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1432117	Environment:
Last Closed:	2017-06-28 14:57:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Container Management	Target Upstream Version:
Embargoed:
Bug Depends On:	1432117
Bug Blocks:

Comment 2 CFME Bot 2017-04-28 20:36:00 UTC

New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/d445d0329c9cbf8f96a35856bbab4625d0dc46e6

commit d445d0329c9cbf8f96a35856bbab4625d0dc46e6
Author:     Martin Povolny <mpovolny>
AuthorDate: Wed Mar 22 11:58:07 2017 +0100
Commit:     Satoe Imaishi <simaishi>
CommitDate: Fri Apr 28 16:34:20 2017 -0400

    Merge pull request #692 from zakiva/fix_volume_link
    
    Fix Persistent Volume link to ems_container
    (cherry picked from commit 6564c612bf353470dd2e74c201ba63933c3d3547)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1436226

 .../layouts/listnav/_persistent_volume.html.haml    |  4 ++--
 .../listnav/_persistent_volume.html.haml_spec.rb    | 21 +++++++++++++++++++++
 2 files changed, 23 insertions(+), 2 deletions(-)
 create mode 100644 spec/views/layouts/listnav/_persistent_volume.html.haml_spec.rb

Comment 3 Einat Pacifici 2017-06-20 11:39:36 UTC

Verified. Clicking on provider in Relationship navigates the user to the provider page

Comment 5 errata-xmlrpc 2017-06-28 14:57:56 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/RHSA-2017:1601