Description of problem:
A few problems have been noticed with the use of the RH CodeReady Workspaces Operator in console e2e testing:
1. There are currently two RH CodeReady Workspaces Operators in OperatorHub! One is for "OCP 4.8+", the other is for "OCP 4.6+" (see screenshot). RH CodeReady Workspaces Operator is used in the OLM e2e tests: `operator-install-single-namespace.spec.ts` and `operator-uninstall.spec.ts`; and in Dev Console's `crw-basic.feature` test.
2. The operator for "OCP 4.8+" no longer supports 'single install' and only installs globally into ns 'openshift-operators'. Fortunately Cypress is continuing to select the "OCP 4.6+" version, so tests continues to pass. THIS WILL START FAILING WHEN the "OCP 4.6+" is removed and "OCP 4.8+ (globall install only)" is the only option available!
3. Recently, the CodeReady workspaces operand tab name has changed from 'CodeReady Workspaces Cluster' to 'CodeReady Workspaces instance Specification' which broke the CI. https://github.com/openshift/console/pull/10247.
#1 & #2 are immediate concerns and another Operator should be found to use in the OLM single-install test. Dev console seems to be using a number of operators, one should be found as a replacment to be used in OLM single-install test: https://github.com/openshift/console/blob/master/frontend/packages/dev-console/integration-tests/support/constants/global.ts#L22
We might be able to use the RH CodeReady Workspaces Operator "OCP 4.8+ (globall install only)" in OLMs `operator-uninstall.spec.ts` test. I think it is just changing a prop in the test to indicate to install globally and changing the namespace the test should look for.
Long Term solution is:
Cypress: Create simple 'Hello World' Operator to use in OLM e2e tests
Wondering how big of a change this will be and if we should not have a techdebt story for it.
steps to verify:
1. checked out the PR
2. run the console test using Cypress
now the test is using the 'Business Automation' operator instead of using the problem causing RH CodeReady Workspaces Operator.
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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.