Bug 1960542 - manifests: invalid selector in ServiceMonitor makes CVO hotloop
Summary: manifests: invalid selector in ServiceMonitor makes CVO hotloop
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Tuning Operator
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Jiří Mencák
QA Contact: Simon
Depends On: 1960337
TreeView+ depends on / blocked
Reported: 2021-05-14 07:31 UTC by OpenShift BugZilla Robot
Modified: 2021-06-15 09:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-06-15 09:27:49 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-node-tuning-operator pull 228 0 None open [release-4.7] Bug 1960542: manifests: fix selector in node-tuning-operator ServiceMonitor 2021-05-17 10:29:51 UTC
Red Hat Product Errata RHSA-2021:2286 0 None None None 2021-06-15 09:28:32 UTC

Comment 3 Simon 2021-06-03 16:27:44 UTC
$ oc get clusterversions.config.openshift.io 
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2021-06-03-004211   True        False         7m37s   Cluster version is 4.7.0-0.nightly-2021-06-03-004211

$ oc -n openshift-cluster-node-tuning-operator get servicemonitors.monitoring.coreos.com -o jsonpath="{.items[0].spec.selector}"

Comment 4 Siddharth Sharma 2021-06-04 18:39:38 UTC
This bug will be shipped as part of next z-stream release 4.7.15 on June 14th, as 4.7.14 was dropped due to a regression https://bugzilla.redhat.com/show_bug.cgi?id=1967614

Comment 8 errata-xmlrpc 2021-06-15 09:27:49 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 (Moderate: OpenShift Container Platform 4.7.16 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.