Bug 1826499 - IngressClass test from upstream is flaky
Summary: IngressClass test from upstream is flaky
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Routing
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Clayton Coleman
QA Contact: Hongan Li
Depends On:
TreeView+ depends on / blocked
Reported: 2020-04-21 19:36 UTC by Clayton Coleman
Modified: 2020-07-13 17:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-07-13 17:29:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24889 0 None closed Bug 1826499: IngressClass error test is flaky 2020-06-23 10:12:12 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:30:10 UTC

Description Clayton Coleman 2020-04-21 19:36:27 UTC
The test assumes that all apiservers are in sync but they can be delayed significantly.

"should prevent Ingress creation if more than 1 IngressClass marked as default"

is the test

Comment 3 Hongan Li 2020-05-06 09:05:44 UTC
Checked latest CI test and didn't see the flaky any more.


Comment 4 errata-xmlrpc 2020-07-13 17:29:56 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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