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

Bug 1734284

Summary:	kube-apiserver ServiceMonitor is still in cluster-monitoring-operator
Product:	OpenShift Container Platform	Reporter:	Junqi Zhao <juzhao>
Component:	Monitoring	Assignee:	Sergiusz Urbaniak <surbania>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.0	CC:	alegrand, anpicker, erooth, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	4.2.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-10-16 06:33:52 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 Junqi Zhao 2019-07-30 07:24:35 UTC

Description of problem:
According to https://jira.coreos.com/browse/MON-670
kube-apiserver ServiceMonitor should be out of cluster-monitoring-operator,
but it is still there

$ oc -n openshift-monitoring get ServiceMonitor | grep kube-apiserver
kube-apiserver                25h

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-28-222114

How reproducible:
Always

Steps to Reproduce:
1. oc -n openshift-monitoring get ServiceMonitor | grep kube-apiserver
2.
3.

Actual results:
kube-apiserver ServiceMonitor is still in cluster-monitoring-operator

Expected results:
kube-apiserver ServiceMonitor should be out of cluster-monitoring-operator

Additional info:

Comment 9 Junqi Zhao 2019-08-27 05:16:39 UTC

# oc -n openshift-monitoring get ServiceMonitor | grep kube-apiserver
kube-apiserver                28h

# oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.2.0-0.nightly-2019-08-25-173945   True        False         28h     Cluster version is 4.2.0-0.nightly-2019-08-25-173945

move back to Assigned

Comment 13 errata-xmlrpc 2019-10-16 06:33:52 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:2922