-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.16.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When UserWorkLoadMonitoring is enabled on the cluster, openshift-lifecycle-agent namespace generates an alert: PrometheusOperatorRejectedResources due missing label openshift.io/cluster-monitoring: true
Version-Release number of selected component (if applicable):
4.16.38
How reproducible:
Always
Steps to Reproduce:
1.Install LCA operator in default namespace (openshift-lifecycle-agent) without any extra options 2. Enable UserWorkLoadMonitoring on the cluster 3.
Actual results:
PrometheusOperatorRejectedResources alert is triggered on the cluster
Expected results:
No alert is triggered
Additional info:
https://issues.redhat.com/browse/OCPBUGS-39126 So as the LCA operator creates a ServiceMonitor, but the namespace does not have openshift.io/cluster-monitoring: true label present, UserWorkloadMonitor will try scrape the metrics, but that is blocked. Compared to other non-community or non-certificed operators the openshift.io/cluster-monitoring: true label is present on the namespace. Tested by labeling the openshift-lifecycle-agent Namespace manually and the alert is not present anymore.
- is related to
-
OCPBUGS-39126 user workload monitoring is trying to scrap RH operators which have been installed in openshift-operators namespace
-
- Closed
-
- links to