-
Bug
-
Resolution: Unresolved
-
Normal
-
4.18, 4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
5
-
None
-
None
-
None
-
None
-
MON Sprint 278, MON Sprint 279
-
2
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-63236. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-62979. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-62160. The following is the description of the original issue:
—
Description of problem:
After disabling the local AlertManager as described in the documentation (https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/monitoring/configuring-core-platform-monitoring), the PrometheusNotConnectedToAlertmanagers alert fires in the cluster and there are still DNS requests failing like this one: [INFO] 10.129.0.18:53183 - 53261 "A IN alertmanager-main.openshift-monitoring.svc.cluster.local. udp 85 false 1232" NXDOMAIN qr,aa,rd 167 0.000069904s It seems that Prometheus still have some AlertManager stuff in the configuration.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
100%
Steps to Reproduce:
1. Disable AlertManager
2. Check that the PrometheusNotConnectedToAlertmanagers
3. Enable trace or debug Level in dns-pods
4. Check dns pod logs. There will be request like this: [INFO] 10.129.0.18:53183 - 53261 "A IN alertmanager-main.openshift-monitoring.svc.cluster.local. udp 85 false 1232" NXDOMAIN qr,aa,rd 167 0.000069904s
Actual results:
The PrometheusNotConnectedToAlertmanagers alert fires. There will be DNS request failing.
Expected results:
When disabling AlertManager, there should not be AlertManager DNS requests or alerts.
Additional info:
- clones
-
-
- POST
-
- is blocked by
-
-
- POST
-
