Bug 1909881

Summary:	Interacting with a global install mode Operator (Portworx Essentials).Interacting with a global install mode Operator (Portworx Essentials) "after all" hook for "uninstalls the operator"
Product:	OpenShift Container Platform	Reporter:	Ben Parees <bparees>
Component:	Management Console	Assignee:	David Taylor <dtaylor>
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.7	CC:	aos-bugs, jhadvig, jokerman, rhamilto
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	Interacting with a global install mode Operator (Portworx Essentials).Interacting with a global install mode Operator (Portworx Essentials) "after all" hook for "uninstalls the operator" job=release-openshift-ocp-installer-console-aws-4.7=all
Last Closed:	2021-01-04 13:48:06 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 Ben Parees 2020-12-21 22:05:39 UTC

test:
Interacting with a global install mode Operator (Portworx Essentials).Interacting with a global install mode Operator (Portworx Essentials) "after all" hook for "uninstalls the operator" 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=Interacting+with+a+global+install+mode+Operator+%5C%28Portworx+Essentials%5C%29%5C.Interacting+with+a+global+install+mode+Operator+%5C%28Portworx+Essentials%5C%29+%22after+all%22+hook+for+%22uninstalls+the+operator%22

sample job:
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-console-aws-4.7/1341010655255203840

output:
AssertionError: Timed out retrying: Expected to find element: `[data-test="portworx-essentials-community-operators-openshift-marketplace"]`, but never found it.
    at Context.eval (https://console-openshift-console.apps.ci-op-6dqz5tj7-c22bb.origin-ci-int-aws.dev.rhcloud.com/__cypress/tests?p=tests/operator-install-global.spec.ts:2251:8)

Looks like there are a number of similar console test failures, will leave it all as one bug for now.

Comment 1 Jakub Hadvig 2020-12-22 09:12:25 UTC

Setting to high priority/severity but not a blocker since its effecting just CI.

Comment 2 David Taylor 2020-12-22 15:31:36 UTC

Robb H's PR to disable the OLM tests:
https://github.com/openshift/console/pull/7623

Other notes:

Robb Hamilton
The CatalogSource for Portworx Essentials is community-operators.  My guess is it is not being added to the cluster in CI?

Dave Taylor
I see @alex (Alexander Greene) added a comment to the PR: "aws console tests were failing due to a community-operators catalog source that was released with limited operators within."

Alexander Greene
Yes - it seems like the Console integration tests with OLM rely on the community operators catalogsource containing the Portworx Essentials operator

Alexander Greene
The test could be updated to create a mock catalog source containing a mock operator that verifies a working OLM UI

Alexander Greene
This would prevent future flakes from happening and remove the UI Test reliance on an external operator controlled by a third party

Robb Hamilton
The Protractor tests had mocks before they were migrated to Cypress.  We were hoping to eliminate the dependency on the mocks.  Apparently, that’s not feasible.  Will work on adding mocks to the Cypress tests.

Robb Hamilton
Looks like we were using https://github.com/openshift/console/blob/f96e815b633cea26b520536b636cf031d131a3e6[…]ager/integration-tests/scenarios/global-installmode.scenario.ts before in Protractor.

Comment 3 Jakub Hadvig 2020-12-23 16:08:43 UTC

We did not have time to fix this issue this sprint. Will reevaluate and try to fix in next sprint.

Comment 4 Robb Hamilton 2021-01-04 13:48:06 UTC


*** This bug has been marked as a duplicate of bug 1909836 ***