Skip to content
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

Bug 1780398: status: performIngressConditionUpdate: Retry on 403 #68

Conversation

Miciah
Copy link
Contributor

@Miciah Miciah commented Dec 6, 2019

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.

  • pkg/router/controller/status.go (performIngressConditionUpdate): Retry on forbidden errors. Never give up retrying after an error.

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-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 6, 2019
@ironcladlou
Copy link
Contributor

Makes sense, thanks!

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 6, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ironcladlou, Miciah

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Miciah Miciah changed the title status: performIngressConditionUpdate: Retry on 403 Bug 1780398: status: performIngressConditionUpdate: Retry on 403 Dec 6, 2019
@openshift-ci-robot
Copy link
Contributor

@Miciah: This pull request references Bugzilla bug 1780398, which is invalid:

  • expected the bug to target the "4.4.0" release, but it targets "4.3.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1780398: status: performIngressConditionUpdate: Retry on 403

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-ci-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Dec 6, 2019
@Miciah
Copy link
Contributor Author

Miciah commented Dec 6, 2019

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Dec 6, 2019
@openshift-ci-robot
Copy link
Contributor

@Miciah: This pull request references Bugzilla bug 1780398, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

/bugzilla refresh

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-merge-robot openshift-merge-robot merged commit a7e5fad into openshift:master Dec 6, 2019
@openshift-ci-robot
Copy link
Contributor

@Miciah: All pull requests linked via external trackers have merged. Bugzilla bug 1780398 has been moved to the MODIFIED state.

In response to this:

Bug 1780398: status: performIngressConditionUpdate: Retry on 403

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.

@Miciah
Copy link
Contributor Author

Miciah commented Dec 9, 2019

/cherrypick release-4.3

@openshift-cherrypick-robot

@Miciah: new pull request created: #70

In response to this:

/cherrypick release-4.3

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants