-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14
-
None
-
+
-
Moderate
-
No
-
MON Sprint 248
-
1
-
False
-
-
.
-
Release Note Not Required
-
Done
This is a clone of issue OCPBUGS-18115. The following is the description of the original issue:
—
Description of problem:
After enabling user-defined monitoring on an HyperShift hosted cluster, PrometheusOperatorRejectedResources starts firing.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Always
Steps to Reproduce:
1. Start an hypershift-hosted cluster with cluster-bot 2. Enable user-defined monitoring 3.
Actual results:
PrometheusOperatorRejectedResources alert becomes firing
Expected results:
No alert firing
Additional info:
Need to reach out to the HyperShift folks as the fix should probably be in their code base.
- blocks
-
OCPBUGS-28247 PrometheusOperatorRejectedResources alert fires on Hypershift clusters with user-defined monitoring
- Closed
- is blocked by
-
OCPBUGS-18115 PrometheusOperatorRejectedResources alert fires on Hypershift clusters with user-defined monitoring
- Closed
- links to
-
RHSA-2023:7198 OpenShift Container Platform 4.15 security update
(1 links to)