Bug 1776193

Summary:	In Developer perspective, graphs should not link to Administrator perspective version of Metrics page
Product:	OpenShift Container Platform	Reporter:	Andrew Pickering <anpicker>
Component:	Management Console	Assignee:	Andrew Pickering <anpicker>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	aos-bugs, jokerman, spadgett, yanpzhan, yapei
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1776186	Environment:
Last Closed:	2020-01-23 11:14: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:	1776186
Bug Blocks:

Description Andrew Pickering 2019-11-25 09:44:58 UTC

+++ This bug was initially created as a clone of Bug #1776186 +++

Description of problem:
When in the Developer perspective, graphs that link to the Metrics page (PromQL query browser page) link to the Administrator perspective version of the Metrics page. They should keep you in the Developer perspective and preserve the currently namespace.

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


How reproducible:
Always

Steps to Reproduce:
1. See description
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Yanping Zhang 2019-12-09 06:31:42 UTC

Tested on OCP 4.3 with payload 4.3.0-0.nightly-2019-12-08-215349. Check "openshift-console" project detail in Developer perspective, click on a graph, it will show metrics in the Developer perspective and current namespace.
The bug is fixed, so move it to "Verified"

Comment 4 errata-xmlrpc 2020-01-23 11:14: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://access.redhat.com/errata/RHBA-2020:0062