-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
feat: add soft errors to pdns provider #4578
feat: add soft errors to pdns provider #4578
Conversation
Add soft errors to pdns provider where it is possible to retry or recover
Welcome @julillae! |
Hi @julillae. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
@@ -208,8 +207,7 @@ func (c *PDNSAPIClient) PatchZone(zoneID string, zoneStruct pgo.Zone) (resp *htt | |||
return resp, err | |||
} | |||
|
|||
log.Errorf("Unable to patch zone. %v", err) | |||
return resp, err | |||
return resp, provider.NewSoftError(fmt.Errorf("unable to patch zone: %v", err)) |
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.
When it fails when trying to update record, after multiple retries, I think this one should be a regular error.
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.
I think this should be a soft error. In a lot of cases, failing to update a record is due to user error. If the error is logged, then a user can "fix" the record definition and it can be applied on another run. Returning a regular error here bubbles up to a fatal error in the controller. Since the error is often recoverable, I think a soft error makes more sense. The AWS provider also returns a soft error when it cannot apply some changes.
/ok-to-test |
/lgtm |
/unassign mloiseleur |
Hello @mloiseleur and @szuecs! I just wanted to ping this PR to see if there is anything I can do to help move it forward. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Raffo 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 |
Add soft errors to pdns provider where it is possible to retry or recover.
Description
Leverages #4166 by adding soft errors to the pdns provider
Checklist