Bug 2044089

Summary: Broken CI: e2e tests doesn't pass anymore after CRW operator was renamed
Product: OpenShift Container Platform Reporter: Christoph Jerolimov <cjerolim>
Component: Dev ConsoleAssignee: Christoph Jerolimov <cjerolim>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: high Docs Contact:
Priority: high    
Version: 4.8CC: aos-bugs, nmukherj, viraj
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-31 18:23:01 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:
Bug Depends On: 2044090    
Bug Blocks: 2044571    
Attachments:
Description Flags
installed-operators-4.9.png
none
prow-status.png none

Description Christoph Jerolimov 2022-01-23 20:12:38 UTC 
Description of problem:
All our 4.9 backports are currently stuck and could not be merged because an e2e test for the CRW integration doesn't pass anymore. The test checks if the exact displayName was part of the "Installed operators" page after installing it.

Version-Release number of selected component (if applicable):
4.9

This only affects 4.9, failing spec file `operator-install-single-namespace.spec.ts` is not part of the master tree anymore.

See also:
https://prow.ci.openshift.org/?repo=openshift%2Fconsole&job=pull-ci-openshift-console-release-4.9-e2e-gcp-console
Comment 1 Christoph Jerolimov 2022-01-23 20:14:01 UTC 
Created attachment 1852907 [details]
installed-operators-4.9.png
Comment 2 Christoph Jerolimov 2022-01-23 20:14:50 UTC 
Created attachment 1852908 [details]
prow-status.png
Comment 4 Vikram Raj 2022-01-24 13:08:24 UTC 
Tests are passing now for 4.9 cherry-picked PR. eg.: https://github.com/openshift/console/pull/10586#issuecomment-1019964540
Comment 8 errata-xmlrpc 2022-01-31 18:23:01 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 (OpenShift Container Platform 4.9.18 bug fix 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.

https://access.redhat.com/errata/RHBA-2022:0279