Bug 2068594 - Cluster Dashboard Details Card integration test failing at high rate
Summary: Cluster Dashboard Details Card integration test failing at high rate
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.11.0
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-25 18:27 UTC by Robb Hamilton
Modified: 2022-04-18 12:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-18 12:41:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11235 0 None open Bug 2068594: fix Cluster Dashboard Details Card test 2022-03-25 18:35:49 UTC
Github openshift console pull 11248 0 None open Bug 2068594: follow on fix to remove timeout value 2022-03-29 12:58:08 UTC
Github openshift console pull 11296 0 None open Bug 2068594: disable Details Card test since it was flaking at a high… 2022-04-06 16:33:06 UTC

Description Robb Hamilton 2022-03-25 18:27:54 UTC 
https://github.com/openshift/console/blob/d7db428edb507bd02a85abe849c61e021c17fdc0/frontend/integration-tests/tests/dashboards/cluster-dashboard.scenario.ts#L20-L50 is failing at a high rate. Investigate and fix.
Comment 4 Robb Hamilton 2022-04-06 15:27:06 UTC 
The test is continuing to flake, so setting it back to assigned.
Comment 8 Robb Hamilton 2022-04-13 13:46:04 UTC 
Note https://github.com/openshift/console/pull/11332 replaces the flaking Protractor test with a Cypress one.  This migration should reduce the flakes and make it easier to troubleshoot and fix flakes if they do occur.
Comment 9 Robb Hamilton 2022-04-18 12:41:47 UTC 
This was fixed by https://github.com/openshift/console/pull/11332, so there is nothing to verify in the PRs that attempted to fix the Protractor version of the test.
Note You need to log in before you can comment on or make changes to this bug.