Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1677398

Summary:	Grafana dashboard unreachable
Product:	OpenShift Container Platform	Reporter:	Mark Schmitt <mschmitt>
Component:	Monitoring	Assignee:	Sergiusz Urbaniak <surbania>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	mloibl, surbania
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-31 02:44:55 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 Mark Schmitt 2019-02-14 18:48:28 UTC

Description of problem:
After installing a cluster with 0.12 installer I'm unable to hit the Grafana dashboard from either Networking/Routes or Monitoring/Dashboard links even though I'm able to access the other monitoring links (alert-manager, openshift-console, and openshift-monitoring).  I've cleared cookies in both Chrome & Firefox but I'm stuck at the log in with Openshift screen for each browser.

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

How reproducible:


Steps to Reproduce:
1.Install cluster with 0.12 installer
2.log into console, attempt to access ->Monitoring - Dashboards
3.clear cookies/restart browsers - same result (stuck on Log in with OpenShift screen)

Actual results:


Expected results:


Additional info:

Comment 3 Junqi Zhao 2019-02-18 11:59:39 UTC

set it to VERIFIED since the same defect Bug 1674346 is fixed

Comment 5 errata-xmlrpc 2019-07-31 02:44:55 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-2019:1866