Description of problem: TestPruneRegistryFlag sometimes panics panic: runtime error: index out of range [0] with length 0 Version-Release number of selected component (if applicable): How reproducible: sometimes Steps to Reproduce: 1. 2. 3. Actual results: panic: runtime error: index out of range [0] with length 0 [recovered] panic: runtime error: index out of range [0] with length 0 goroutine 1557 [running]: testing.tRunner.func1(0xc000291500) /usr/local/go/src/testing/testing.go:874 +0x3a3 panic(0x19541e0, 0xc00073c920) /usr/local/go/src/runtime/panic.go:679 +0x1b2 github.com/openshift/cluster-image-registry-operator/test/e2e.TestPruneRegistryFlag(0xc000291500) /go/src/github.com/openshift/cluster-image-registry-operator/test/e2e/pruner_test.go:55 +0xafc testing.tRunner(0xc000291500, 0x1b43d50) /usr/local/go/src/testing/testing.go:909 +0xc9 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:960 +0x350 FAIL github.com/openshift/cluster-image-registry-operator/test/e2e 1384.405s Expected results: green tests Additional info:
QE watches 5+ jobs and no panic now, like: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/543/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/2595 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/2603
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