-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.21
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-63175. The following is the description of the original issue:
—
Description of problem
The HostedCluster cluster-node-tuning-operator Pod does not currently serve metrics on 60000, which means the node-tuning-operator ServiceMonitor is not functional. OCPBUGS-55399 is tracking a fix for that issue, but until that fix is sorted, this ticket is tracking removing the non-functional ServiceMonitor, to avoid confusing system ah2.dministrators and hypershift#6965's metrics test coverage. TheServiceMonitor can be restored via OCPBUGS-55399 once it's working.
Version-Release number of selected component
Definitely 4.21, as seen in hypershift#6965 presubmits. Likely also older 4.y; I haven't gone hunting in Git history or CI results.
How reproducible
Every time.
Steps to Reproduce
1. Create Hosted Cluster
2. Check that a node-tuning-operator ServiceMonitor exists.
3. Check the up metric for any job label that includes node-tuning.
Actual results
The ServiceMonitor exists, but the up metric for that job is 0 or does not exist.
Expected results
Short term in this bug series, the ServiceMonitor does not exist (even in clusters installed in older releases and then updated to the release that fixes this series).
Longer term in the OCPBUGS-55399 bug series, the ServiceMonitor does exist, and is successfully getting scraped so an up metric is giving 1 for the node-tuning job label.
- clones
-
OCPBUGS-63175 Non-functional HostedCluster node-tuning-operator ServiceMonitor should be removed
-
- MODIFIED
-
- is blocked by
-
OCPBUGS-63175 Non-functional HostedCluster node-tuning-operator ServiceMonitor should be removed
-
- MODIFIED
-
- links to