Bug 2029369 - Cypress tests github rate limit errors
Summary: Cypress tests github rate limit errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.10.0
Assignee: Jan Richter
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-06 10:26 UTC by Jan Richter
Modified: 2022-03-10 16:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:32:18 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10599 0 None open Bug 2029369: Mock github API requests when importing projects in cypress tests 2021-12-06 10:27:37 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:32:33 UTC

Description Jan Richter 2021-12-06 10:26:39 UTC 
Description of problem:
Cypress tests (including e2e addFlow tests) may run into github rate limits when creating workloads using import from git.


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


How reproducible:
Intermittent on CI
With enough reruns locally, always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Christoph Jerolimov 2022-01-04 10:06:58 UTC 
Mark it as verified because the PR only affects our integration tests.
Comment 6 errata-xmlrpc 2022-03-10 16:32:18 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.

https://access.redhat.com/errata/RHSA-2022:0056
Note You need to log in before you can comment on or make changes to this bug.