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:
# 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
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