Bug 2105328 - crud/other-routes.spec.ts Cypress test failing at a high rate in CI
Summary: crud/other-routes.spec.ts Cypress test failing at a high rate in CI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.12.0
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 2106594
TreeView+ depends on / blocked
 
Reported: 2022-07-08 14:50 UTC by Robb Hamilton
Modified: 2023-01-17 19:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
No end user impact.
Clone Of:
Environment:
Last Closed: 2023-01-17 19:51:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11809 0 None open Bug 2105909, Bug 2105328: Fix create-namespace e2e test, ESOCKET timeout issue, and a11y violations to unblock CI 2022-07-12 17:00:15 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:52:34 UTC

Internal Links: 2117642

Description Robb Hamilton 2022-07-08 14:50:09 UTC
Description of problem:  The crud/other-routes.spec.ts Cypress test is failing in CI at a high rate, blocking the merging of many PRs.  The error is as follows:

successfully displays view for route: : Visiting other routes successfully displays view for route:  expand_less	18s
{1 accessibility violation was detected: expected 1 to equal 0 AssertionError AssertionError: 1 accessibility violation was detected: expected 1 to equal 0
    at Context.checkA11y (https://console-openshift-console.apps.ci-op-dr66twys-75d12.XXXXXXXXXXXXXXXXXXXXXX/__cypress/tests?p=tests/crud/other-routes.spec.ts:10176:10)}


Version-Release number of selected component (if applicable):  4.12, 4.11

Comment 1 Robb Hamilton 2022-07-08 14:52:22 UTC
Upon investigation, I suspect the failure is occurring because <ServiceLevel> can return nodes that are not <dt> or <dd>, causing an a11y failure.

Comment 4 xiangyli 2022-07-21 10:30:09 UTC
https://search.ci.openshift.org/?search=accessibility+violation+was+detected&maxAge=336h&context=1&type=junit&name=pull-ci-openshift-console-master-e2e-gcp-console&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
https://search.ci.openshift.org/?search=accessibility+violation+was+detected&maxAge=168h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

These two links, where the first link shows that the PR which is merged 8 days ago stopped the accessibility violation to appear in the 4.12 version. 

However, it seems I have to wait for some time, since the 4.11 release is merged only 22 hours ago at the time of writing this comment. I will follow up the verification when more job logs are produced.

Comment 8 errata-xmlrpc 2023-01-17 19:51:48 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.12.0 bug fix and 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.

https://access.redhat.com/errata/RHSA-2022:7399


Note You need to log in before you can comment on or make changes to this bug.