Bug 2015952

Summary: RH CodeReady Workspaces Operator in e2e testing will soon fail
Product: OpenShift Container Platform Reporter: David Taylor <dtaylor>
Component: Management ConsoleAssignee: David Taylor <dtaylor>
Status: CLOSED ERRATA QA Contact: Siva Reddy <schituku>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.10CC: aos-bugs, yapei
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:21: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:

Description David Taylor 2021-10-20 13:04:17 UTC
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

Comment 2 Jakub Hadvig 2021-10-21 08:49:10 UTC
Wondering how big of a change this will be and if we should not have a techdebt story for it.

Comment 5 Siva Reddy 2021-11-04 21:42:12 UTC


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.

Comment 9 errata-xmlrpc 2022-03-10 16:21:06 UTC
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.