https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/458/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/2444 === RUN TestNodeCAGracefulShutdown --- FAIL: TestNodeCAGracefulShutdown (1.34s) logs.go:114: Get https://10.0.130.63:10250/containerLogs/openshift-image-registry/node-ca-8dmbs/node-ca?follow=true: dial tcp 10.0.130.63:10250: connect: connection refused
few more examples: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/469/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/2428 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/466/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/2423
Verified with https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/542/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/2602
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409