-
Notifications
You must be signed in to change notification settings - Fork 115
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
[release-4.3] Bug 1781313: status: performIngressConditionUpdate: Retry on 403 #70
[release-4.3] Bug 1781313: status: performIngressConditionUpdate: Retry on 403 #70
Conversation
If a status update fails with a forbidden error, retry the update. Keep retrying failed updates as long as the route has the wrong status. This commit fixes bug 1780398. https://bugzilla.redhat.com/show_bug.cgi?id=1780398 * pkg/router/controller/status.go (performIngressConditionUpdate): Retry on forbidden errors. Never give up retrying after an error.
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1780398, which is invalid:
Comment 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. |
/retitle [release-4.3] Bug 1781313: status: performIngressConditionUpdate: Retry on 403 |
@openshift-cherrypick-robot: An error was encountered adding this pull request to the external tracker bugs for bug 1781313 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
/bugzilla refresh |
@Miciah: An error was encountered adding this pull request to the external tracker bugs for bug 1781313 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ironcladlou, openshift-cherrypick-robot 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 |
/bugzilla refresh |
@ironcladlou: This pull request references Bugzilla bug 1781313, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 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. |
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged. Bugzilla bug 1781313 has been moved to the MODIFIED state. 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. |
This is an automated cherry-pick of #68
/assign Miciah