-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
None
-
None
job link
snippet from test output:
{ 1 events happened too frequently
event happened 28 times, something is wrong: ns/openshift-machine-api pod/machine-api-controllers-77fb6ff9f7-84bfw node/ip-10-0-242-241.us-east-2.compute.internal - reason/ProbeError Readiness probe error: Get "http://10.130.0.20:9441/healthz": dial tcp 10.130.0.20:9441: connect: connection refused
body:
}
This failure is coming from a check that "[sig-arch] events should not repeat pathologically". Essentially looking for troubling events
that occur more than X (I think it's 20) number of times. This particular issue of "connection refused" on Readiness probe seems
to happen in our ovn-upgrade job periodicially. I only saw one case of it happening in an openshift-sdn job and that was in a
slightly more complicated upgrade-rollback job. I think this one is worth chasing down since it seems someone affected by
ovn.
here's a search.ci link that shows all the jobs that have this problem for our aws-ovn-upgrade jobs over the last 7 days.
link to this job's testgrid for reference.
