Bug 1834995

Summary:	olmFull suite always fails once th suite is run on the same cluster
Product:	OpenShift Container Platform	Reporter:	Hiro Miyamoto <hmiyamot>
Component:	Management Console	Assignee:	Robb Hamilton <rhamilto>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.5	CC:	aos-bugs, jokerman, yanpzhan
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	This is for an intergration test and is not a customer-facing issue.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:12:13 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 Hiro Miyamoto 2020-05-12 20:34:36 UTC

Description of problem:
Integration test scenario "global-installmode.scenario.ts" fails if run multiple times on the same cluster

Version-Release number of selected component (if applicable):
Tested on "devclusters" from CoreOS #forum-ui-clusters on multiple days in early May 2020

How reproducible:
Always

Steps to Reproduce:
1. Prime environment to run integration/e2e tests per https://github.com/openshift/console/blob/master/README.md
2. Run "olmFull" suite once (eg. ./test-gui.sh olmFull)
3. Run "olmFull" suite again

Actual results:
Whether the first run succeeds or not, all subsequent runs fail early in the "All Namespaces (Jaeger)" part, perhaps at "displays Operator in "Cluster Service Versions" view for "test-xsmrb" namespace"

Expected results:
All subsequent runs should have the same chance of passing as the first

Additional info:

Comment 1 bpeterse 2020-05-13 18:06:33 UTC

Test updates are good candidates to migrate to Cypress.

Comment 2 Zac Herman 2020-05-13 18:28:40 UTC

This does not affect CI currently, so I am marking it 4.6 since we need to redo this entire test in cypress once it merges.  If there is time, we will come back to this for 4.5.

Comment 3 Zac Herman 2020-05-29 15:39:32 UTC

This is still a 4.6 target and therefore will move to future sprint.

Comment 4 Zac Herman 2020-08-20 21:52:42 UTC

Work in progress but will need until next sprint.

Comment 5 Zac Herman 2020-10-22 15:32:43 UTC

Due to the size of this fix, we have a jira ticket console-2397 tracking this work. 
 Will not be done this sprint so moving to next sprint.

Comment 6 Robb Hamilton 2020-11-19 15:17:57 UTC

This was fixed by porting the tests over to Cypress and removing the Protractor-based test suite this bug was filed against.  Waiting on https://github.com/openshift/console/pull/7261 to merge before updating status.

Comment 7 Yanping Zhang 2020-11-26 10:06:48 UTC

Build against console master branch locally, then run olm integration test several times: # ./test-cypress.sh -p olm 
The results for all runs passed at most steps except some timeout failure. The latter runs won't fail early now, the bug is fixed.

Comment 10 errata-xmlrpc 2021-02-24 15:12:13 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.7.0 security, bug fix, and enhancement 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/RHSA-2020:5633