OCPBUGS-113581: Raise status polling timeout and write bound - #31553
OCPBUGS-113581: Raise status polling timeout and write bound#31553redhat-chai-bot wants to merge 1 commit into
Conversation
The 3-replica conflicting router stress test was intermittently failing in two independent places. 1. Polling timeout 2m -> 5m: the leader election lease lasts 1 minute. Under normal conditions all route statuses are written within 1-2 lease cycles, which fit in the previous 2-minute timeout. Under heavier contention a router replica may need to re-acquire the lease 3 or more times until all routes are updated. 2. Write upper bound 50 -> 75: the per-route contention detector runs asynchronously and can lag behind update events, allowing a few extra writes before suppressing further updates. The previous limit of 50 caused intermittent failures; 75 is a more conservative ceiling. https://redhat.atlassian.net/browse/OCPBUGS-99536
|
@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-99536, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: redhat-chai-bot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-113581, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@dustman9000: This pull request references Jira Issue OCPBUGS-113581, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Fix included in release 5.1.0-0.nightly-2026-08-24-111752 |
|
@redhat-chai-bot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/retest-required AI-generated. Review for accuracy. |
Summary
Cherry-pick of #31534 to
release-4.20.Fixes flaky test
[sig-network][Feature:Router] The HAProxy router converges when multiple routers are writing conflicting statusby raising two thresholds intest/extended/router/stress.go:This test caused 367 failures in a single 7-day window before the fix landed on
main. The 4.20 nightlye2e-rosa-sts-ovnjob continues to hit this flake (most recently with 52 writes vs the 50 limit).References
test/extended/router/stress.go(10 additions, 4 deletions)AI-generated. Review for accuracy.
@dustman9000 requested in Slack thread