We're seeing frequent test failures on https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_console/6192/pull-ci-openshift-console-master-e2e-gcp-console/1290655774648832000 https://search.ci.openshift.org/?search=%E2%9C%96+displays+Operator+as+subscribed+in+OperatorHub+&maxAge=48h&context=1&type=build-log&name=&maxMatches=5&maxBytes=20971520&groupBy=job
Queue appears to be broken, raising severity.
Updating the title since this appears to be a real bug (and a symptom of bug 1814822).
I saw there is still some similar failed logs in https://search.ci.openshift.org/?search=%E2%9C%96+displays+Operator+as+subscribed+in+OperatorHub+&maxAge=48h&context=1&type=build-log&name=&maxMatches=5&maxBytes=20971520&groupBy=job Such as https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_console/6272/pull-ci-openshift-console-master-e2e-gcp-console/1293295839287971840 Log is raised at 2020-08-11 21:18:53 +0000 UTC Failed Specs: 1) Interacting with an `AllNamespaces` install mode Operator (Jaeger) : displays Operator as subscribed in OperatorHub TimeoutError: Wait timed out after 20000ms at /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:2201:17 at ManagedPromise.invokeCallback_ /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:1376:14 at TaskQueue.execute_ /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:3084:14 at TaskQueue.executeNext_ /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:3067:27 at asyncRun /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:2927:27 skipped 77 lines unfold_more 2020/08/11 22:22:20 Container test in pod e2e-gcp-console failed, exit code 1, reason Error 2020/08/11 22:35:27 Copied 159.34MB of artifacts from e2e-gcp-console to /logs/artifacts/e2e-gcp-console 2020/08/11 22:35:27 Releasing lease for "gcp-quota-slice" 2020/08/11 22:35:27 No custom metadata found and prow metadata already exists. Not updating the metadata. 2020/08/11 22:35:27 Ran for 1h16m2s error: some steps failed: * could not run steps: step e2e-gcp-console failed: template pod "e2e-gcp-console" failed: the pod ci-op-krsdrhcx/e2e-gcp-console failed after 1h6m49s (failed containers: test): ContainerFailed one or more containers exited Container test exited with code 1, reason Error Could you help to have a check?
We fixed one issue, but there are still some other flakes being tracked under bug 1866296. I'm going to duplicate this one to that bug. *** This bug has been marked as a duplicate of bug 1866296 ***