-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.13
This is a clone of issue OCPBUGS-36717. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-31250. The following is the description of the original issue:
—
Description of problem:
1. For the Linux nodes, the container runtime is CRI-O and the port 9537 has a crio process listening on it.While, windows nodes doesn't have CRIO container runtime.
2. Prometheus is trying to connect to /metrics endpoint on the windows nodes on port 9537 which actually does not have any process listening on it.
3. TargetDown is alerting crio job since it cannot reach the endpoint http://windows-node-ip:9537/metrics.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Install 4.13 cluster with windows operator 2. In the Prometheus UI, go to > Status > Targets to know which targets are down.
Actual results:
It gives the alert for targetDown
Expected results:
It should not give any such alert.
Additional info:
- blocks
-
OCPBUGS-42603 alert for metrics endpoint at port 9537 shows connection refused for windows nodes
- Closed
- clones
-
OCPBUGS-36717 alert for metrics endpoint at port 9537 shows connection refused for windows nodes
- Closed
- is blocked by
-
OCPBUGS-36717 alert for metrics endpoint at port 9537 shows connection refused for windows nodes
- Closed
- is cloned by
-
OCPBUGS-42603 alert for metrics endpoint at port 9537 shows connection refused for windows nodes
- Closed
- links to
-
RHBA-2024:7594 OpenShift Container Platform 4.15.z bug fix update