Bug 1684407

Summary:	Missing auth Prometheus endpoint coverage
Product:	OpenShift Container Platform	Reporter:	Chuan Yu <chuyu>
Component:	apiserver-auth	Assignee:	Erica von Buelow <evb>
Status:	CLOSED ERRATA	QA Contact:	scheng
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, nagrawal, scheng
Target Milestone:	---	Keywords:	TestBlocker
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-06-04 10:44:51 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 Chuan Yu 2019-03-01 08:09:16 UTC

Description of problem:
In 3.x there are some auth Prometheus endpoint coverage, such as, openshift_auth_basic_password_count, openshift_auth_basic_password_count_result, openshift_auth_form_password_count and openshift_auth_form_password_count_result, but all missing in 4.0

Version-Release number of selected component (if applicable):
$ oc get clusterversion
NAME      VERSION     AVAILABLE   PROGRESSING   SINCE     STATUS
version   4.0.0-0.6   True        False         44m       Cluster version is 4.0.0-0.6

How reproducible:
always

Steps to Reproduce:
Setup OCP 4.0 cluster, and open Prometheus console, try to query some auth endpoint

Actual results:
Missing auth Prometheus endpoint  

Expected results:
Should have auth Prometheus endpoint coverage

Additional info:

Comment 2 Neelesh Agrawal 2019-03-26 16:42:53 UTC

https://github.com/openshift/cluster-authentication-operator/pull/92

Comment 4 scheng 2019-04-17 06:52:33 UTC

There is still no successful nightly builds contain the PR(https://github.com/openshift/cluster-authentication-operator/pull/92).
Will verify this ASAP.

Comment 5 scheng 2019-04-19 06:10:37 UTC

Verified

Comment 7 errata-xmlrpc 2019-06-04 10:44:51 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:0758