Bug 1623778

Summary: [3.11] Redundant form in the prometheus-k8s route UI page
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: MonitoringAssignee: Frederic Branczyk <fbranczy>
Status: CLOSED WONTFIX QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: low    
Version: 3.11.0CC: kgeorgie
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1669392 (view as bug list) Environment:
Last Closed: 2019-10-23 13:25:15 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:
Bug Depends On:    
Bug Blocks: 1669392    
Attachments:
Description Flags
prometheus k8s route none

Description Junqi Zhao 2018-08-30 08:00:34 UTC
Created attachment 1479712 [details]
prometheus k8s route

Description of problem:
This issue is copied from Jira defect MON-272, moved here to track issue better.

Log in prometheus-k8s route, besides the "Log in with OpenShift" button, there is one form under it, input name and password, the url navigates to /oauth/sign_in, but the page is still the same with  prometheus-k8s route, shall the form be deleted or hidden?

Other routes don't have this problem

$ oc get route
NAME                HOST/PORT                                                             PATH      SERVICES            PORT      TERMINATION   WILDCARD
alertmanager-main   alertmanager-main-openshift-monitoring.apps.0730-hjd.qe.rhcloud.com             alertmanager-main   web       reencrypt     None
grafana             grafana-openshift-monitoring.apps.0730-hjd.qe.rhcloud.com                       grafana             https     reencrypt     None
prometheus-k8s      prometheus-k8s-openshift-monitoring.apps.0730-hjd.qe.rhcloud.com                prometheus-k8s      web       reencrypt     None

Comments from Frederic Branczyk:
This is sadly not something we can control. This is due to the way Grafana authenticates with Prometheus. In future versions this will go away as we will change the way Grafana authenticates with Prometheus, but for 3.11, this works as intended.

Version-Release number of selected component (if applicable):
cluster monitoring images version
v3.11.0-0.25.0.0

# openshift version
openshift v3.11.0-0.25.0


How reproducible:
Always

Steps to Reproduce:
1. Login prometheus-k8s route
2.
3.

Actual results:


Expected results:


Additional info: