Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1829910

Summary: [ci] e2e tests panics
Product: OpenShift Container Platform Reporter: Oleg Bulatov <obulatov>
Component: Image RegistryAssignee: Oleg Bulatov <obulatov>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:33:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Oleg Bulatov 2020-04-30 14:46:47 UTC
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:

Comment 4 errata-xmlrpc 2020-07-13 17:33:40 UTC
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