Description of problem: The test: it(`displays Operator in "Cluster Service Versions" view for "${testName}" namespace`, async () => { in console/frontend/packages/operator-lifecycle-manager/integration-tests/scenarios/single-installmode.scenario.ts frequently flakes. We need to explore what causes this test to fail. How reproducible: Inconsistently, its a flake. Some examples: https://search.svc.ci.openshift.org/?search=+%E2%9C%96+displays+Operator+in&maxAge=168h&context=1&type=build-log&name=&maxMatches=5&maxBytes=20971520 70 results in a week is a lot of failures. Expected results: e2e tests should run regularly without failure or flakes.
We haven't seen any occurrences of this flake since we increased the timeout in https://github.com/openshift/console/pull/4982
https://search.svc.ci.openshift.org/?search=+%E2%9C%96+displays+Operator+in&maxAge=168h&context=1&type=build-log&name=&maxMatches=5&maxBytes=20971520 There are 21 times failure over 7 days due to this issue. The timeout increasing indeed helps this. example: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_console/4830/pull-ci-openshift-console-master-e2e-gcp-console/16668 However do you think if we need add longer timeout to decrease the failure occurrences?
ignore my above comment, I re-checked the search link and just find one time failure after the pr merge. So we can verify this bug.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days