Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-529

watcher: investigate "Readiness probe error on pod/openshift-config-operator"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • False
    • None
    • False

      https://amd64.ocp.releases.ci.openshift.org/releasestream/4.12.0-0.ci/release/4.12.0-0.ci-2022-09-01-053740

       

      https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/aggregated-aws-ovn-upgrade-4.12-minor-release-openshift-release-analysis-aggregator/1565212595130994688

       

      There are a lot of probe errors like this in the failures on that aggregated job; a lot of them are on pod/openshift-config-operator

      event happened 23 times, something is wrong: ns/openshift-config-operator pod/openshift-config-operator-68d5885c8f-68bkq node/ip-10-0-147-250.us-east-2.compute.internal - reason/ProbeError Readiness probe error: Get "https://10.128.0.23:8443/healthz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
      body: 
      } 

              dperique@redhat.com Dennis Periquet
              dperique@redhat.com Dennis Periquet
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: