Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-42603

alert for metrics endpoint at port 9537 shows connection refused for windows nodes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.14.z
    • 4.13
    • Monitoring
    • Moderate
    • No
    • MON Sprint 260
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, if a connection on port 9637 for Windows nodes was refused, the Kubelet Service Monitor threw a `target down` alert because CRI-O does not run on Windows nodes. With this release, Windows nodes are excluded from the Kubelet Service Monitor. (link:https://issues.redhat.com/browse/OCPBUGS-42603[*OCPBUGS-42603*])
      Show
      * Previously, if a connection on port 9637 for Windows nodes was refused, the Kubelet Service Monitor threw a `target down` alert because CRI-O does not run on Windows nodes. With this release, Windows nodes are excluded from the Kubelet Service Monitor. (link: https://issues.redhat.com/browse/OCPBUGS-42603 [* OCPBUGS-42603 *])
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-42586. The following is the description of the original issue:
      —
      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:

              janantha@redhat.com Jayapriya Pai
              openshift-crt-jira-prow OpenShift Prow Bot
              Junqi Zhao Junqi Zhao
              Simon Pasquier
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: