New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issue where wildcard routes get 503s intermittently. #22087
Fix issue where wildcard routes get 503s intermittently. #22087
Conversation
As part of the resync processing, wildcard routes get a "HostAlreadyClaimed" error and then later as part of the same event processing flow, the route gets re-added. This results in a temporary outage (route returns 503s). fixes #1660647 (https://bugzilla.redhat.com/show_bug.cgi?id=1660647)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ironcladlou, pravisankar, ramr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherrypick release-3.10 |
|
/cherrypick release-3.9 |
|
@ramr: #22087 failed to apply on top of branch "release-3.10": In 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 kubernetes/test-infra repository. |
|
@ramr: #22087 failed to apply on top of branch "release-3.9": In 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 kubernetes/test-infra repository. |
As part of the resync processing, wildcard routes get a "HostAlreadyClaimed"
error and then later as part of the same event processing flow, the route gets re-added.
This results in a temporary outage (route returns 503s).
fixes #1660647 (https://bugzilla.redhat.com/show_bug.cgi?id=1660647)
@openshift/sig-network-edge PTAL Thx
Edited clarified route gets added in the same event processing flow.