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 1756303: dns/aws: Do not include record in error messages #305

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #304

/assign ironcladlou

Do not include the DNSRecord resource in the error message that the AWS DNS
provider returns in the case of a zone-lookup failure.

The DNS controller incorporates the error message from the DNS provider
into the DNSRecord resource's "Failed" status condition message, which
caused problems in the case of repeated zone-lookup failures.  Before this
commit, such a failure would cause the controller to update the status
condition message to include the DNSRecord from the previous failure, which
would have a status condition message with the DNSRecord from the second
previous failure, which would have a status condition message with the
DNSRecord from the third previous failure, and so on.  As a result, the DNS
controller was making many spurious updates with increasingly long status
condition messages, to the point that etcd began rejecting updates with
"request is too large".

* pkg/dns/aws/dns.go (change): Omit the DNSRecord from the error message
for zone-lookup failure.
@openshift-ci-robot openshift-ci-robot added bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 27, 2019
@ironcladlou ironcladlou changed the title [release-4.2] Bug 1756302: dns/aws: Do not include record in error messages Bug 1756303: dns/aws: Do not include record in error messages Sep 27, 2019
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1756303, which is invalid:

  • expected dependent Bugzilla bug 1756302 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is MODIFIED 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 1756303: dns/aws: Do not include record in error messages

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.

@ironcladlou
Copy link
Contributor

/hold

We're going to let this one wait for a z-stream.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 27, 2019
@knobunc
Copy link

knobunc commented Sep 27, 2019

/approve

@knobunc
Copy link

knobunc commented Sep 27, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Sep 27, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knobunc, 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift openshift deleted a comment from openshift-ci-robot Sep 27, 2019
@ironcladlou
Copy link
Contributor

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@ironcladlou: This pull request references Bugzilla bug 1756303, which is valid.

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-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 Oct 17, 2019
@knobunc
Copy link

knobunc commented Oct 18, 2019

/hold cancel

This can now follow the normal z-stream process.

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 18, 2019
@jwforres jwforres added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 21, 2019
@openshift-merge-robot openshift-merge-robot merged commit 2a6afce into openshift:release-4.2 Oct 22, 2019
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged. Bugzilla bug 1756303 has been moved to the MODIFIED state.

In response to this:

Bug 1756303: dns/aws: Do not include record in error messages

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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

7 participants