The must gather pod launched by the CI is causing the crashlooping pods test to fail. It may be that the test should ignore pods that are run once and have no failing containers, but should be investigated. https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.1/340 [Feature:Platform] Managed cluster should have no crashlooping pods in core namespaces over two minutes [Suite:openshift/conformance/parallel] 2m2s fail [github.com/openshift/origin/test/extended/operators/cluster.go:109]: Expected <[]string | len:1, cap:1>: [ "Pod openshift-must-gather-hzg6c/must-gather-tnvmr was pending entire time: unknown error", ] to be empty
Occurs when crashlooping pods test and must-gather test run concurrently. Fixed by: https://github.com/openshift/origin/pull/22712
*** Bug 1704470 has been marked as a duplicate of this bug. ***
Fixed in 4.1.0
Confirmed with latest payload, the issue has fixed: Payload: 4.1.0-0.nightly-2019-05-14-202907 Open 2 terminals, at the same time, one run `oc adm must-gather` , other one run `openshift-tests run-test "[Feature:Platform] Managed cluster should have no crashlooping pods in core namespaces over two minutes [Suite:openshift/conformance/parallel]" ` . no error found.
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-2019:0758