Description of problem: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_cluster-etcd-operator/350/pull-ci-openshift-cluster-etcd-operator-master-e2e-aws-disruptive/420/build-log.txt Test code is causing a panic: May 14 18:16:28.759: INFO: Running AfterSuite actions on node 1 /usr/local/go/src/runtime/panic.go:679 +0x1b2 github.com/openshift/origin/test/extended/dr.constructEtcdConnectionString(0xc001ee23e8, 0x1, 0x1, 0x0, 0x0) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/dr/common.go:80 +0x68a github.com/openshift/origin/test/extended/dr.glob..func1.1.1() /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/dr/quorum_restore.go:107 +0x605 github.com/openshift/origin/test/extended/util/disruption.Run.func1() /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/util/disruption/disruption.go:65 +0xe7 github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/chaosmonkey.(*Chaosmonkey).Do(0xc001dda950) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/chaosmonkey/chaosmonkey.go:111 +0x38a github.com/openshift/origin/test/extended/util/disruption.runChaosmonkey(0xc002710950, 0x0, 0x0, 0x0, 0x0, 0xc002710ad0, 0x6, 0x6, 0xc000cabd10) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/util/disruption/disruption.go:115 +0x437 github.com/openshift/origin/test/extended/util/disruption.Run(0x5a00363, 0x17, 0x59c8b4e, 0xe, 0x0, 0x0, 0x0, 0x0, 0xc002710ad0, 0x6, ...) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/util/disruption/disruption.go:67 +0x1fd github.com/openshift/origin/test/extended/dr.glob..func1.1() /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/dr/quorum_restore.go:80 +0x72f github.com/openshift/origin/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc001751d40, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/cmd/openshift-tests/openshift-tests.go:239 +0x4e github.com/openshift/origin/test/extended/util.WithCleanup(0xc001e49bd8) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/util/test.go:166 +0x58 main.newRunTestCommand.func1(0xc001674c80, 0xc00113b3e0, 0x1, 0x1, 0x0, 0x0) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/cmd/openshift-tests/openshift-tests.go:239 +0x1be github.com/openshift/origin/vendor/github.com/spf13/cobra.(*Command).execute(0xc001674c80, 0xc00113b3a0, 0x1, 0x1, 0xc001674c80, 0xc00113b3a0) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/github.com/spf13/cobra/command.go:826 +0x460 github.com/openshift/origin/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc001674500, 0x0, 0x6658ce0, 0xa0c2910) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/github.com/spf13/cobra/command.go:914 +0x2fb github.com/openshift/origin/vendor/github.com/spf13/cobra.(*Command).Execute(...) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/github.com/spf13/cobra/command.go:864 main.main.func1(0xc001674500, 0x0, 0x0) /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/cmd/openshift-tests/openshift-tests.go:61 +0x9c main.main() /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/cmd/openshift-tests/openshift-tests.go:62 +0x36e fail [runtime/panic.go:679]: Test Panicked: runtime error: index out of range [1] with length 1 failed: (5m1s) 2020-05-14T18:16:28 "[sig-etcd][Feature:DisasterRecovery][Disruptive] [Feature:EtcdRecovery] Cluster should restore itself after quorum loss [Serial] [Suite:openshift]" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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