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

[release-4.14] OCPBUGS-28200: UPSTREAM: 6277: openshift: Fix OCPBUGS-28200 #114

Merged

Conversation

gcs278
Copy link

@gcs278 gcs278 commented Jan 30, 2024

4.14 Cherry-Pick of coredns#6277 which fixes OCPBUGS-28200 by adding logic that more gracefully handles overflow errors by setting the Truncated Bit and clearing the response. This indicates to DNS clients to retry with TCP, whereas previously they would have always gotten a SERVFAIL.

This becomes more important/exposed with CoreDNS 1.10.1 (OCP 4.13) onwards, given the changes introduced by coredns#5671. This modification only uses EDNS on the upstream DNS request when the client query used EDNS. It appears that certain DNS resolvers may not handle non-EDNS queries in a compliant manner.

Cherry-Pick Merge Conflict:

CONFLICT (modify/delete): plugin/pkg/proxy/proxy_test.go deleted in HEAD and modified in 37a9afe69 (UPSTREAM: 6277: openshift: Fix OCPBUGS-27397).  Version 37a9afe69 (UPSTREAM: 6277: openshift: Fix OCPBUGS-27397) of plugin/pkg/proxy/proxy_test.go left in tree.
  • plugin/pkg/proxy directory doesn't exist in release-4.14 due to refactoring, so I placed the unit tests in plugin/forward/proxy_test.go
  • Required some refactoring due to function signature changes and other refactoring

Handle UDP responses that overflow with TC bit with test case (coredns#6277)

Signed-off-by: SriHarshaBS001 <SriHarshaBS009@gmail.com>
Modified-by: Grant Spence <gspence@redhat.com>
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 30, 2024
@openshift-ci openshift-ci bot requested review from knobunc and Miciah January 30, 2024 21:12
@gcs278
Copy link
Author

gcs278 commented Jan 30, 2024

/close

@openshift-ci openshift-ci bot closed this Jan 30, 2024
Copy link

openshift-ci bot commented Jan 30, 2024

@gcs278: Closed this PR.

In response to this:

/close

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.

@gcs278
Copy link
Author

gcs278 commented Jan 31, 2024

/reopen

@gcs278
Copy link
Author

gcs278 commented Jan 31, 2024

/open

@openshift-ci openshift-ci bot reopened this Jan 31, 2024
Copy link

openshift-ci bot commented Jan 31, 2024

@gcs278: Reopened this PR.

In response to this:

/reopen

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.

@gcs278 gcs278 changed the title [WIP] Ocpbugs 27397 4.14 [WIP] [new-branch-name] [release-4.14] OCPBUGS-28200: UPSTREAM: 6277: openshift: Fix OCPBUGS-28200 Jan 31, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 31, 2024
@openshift-ci-robot
Copy link

@gcs278: This pull request references Jira Issue OCPBUGS-28200, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-27904 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-27904 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Handle UDP responses that overflow with TC bit with test case (coredns#6277)

Modified-by: Grant Spence gspence@redhat.com

1. Why is this pull request needed and what does it do?

2. Which issues (if any) are related?

3. Which documentation changes (if any) need to be made?

4. Does this introduce a backward incompatible change or deprecation?

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link

openshift-ci bot commented Jan 31, 2024

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: melvinjoseph86.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@gcs278: This pull request references Jira Issue OCPBUGS-28200, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-27904 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-27904 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Handle UDP responses that overflow with TC bit with test case (coredns#6277)

Modified-by: Grant Spence gspence@redhat.com

1. Why is this pull request needed and what does it do?

2. Which issues (if any) are related?

3. Which documentation changes (if any) need to be made?

4. Does this introduce a backward incompatible change or deprecation?

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 openshift-eng/jira-lifecycle-plugin repository.

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.

@gcs278 gcs278 changed the title [WIP] [new-branch-name] [release-4.14] OCPBUGS-28200: UPSTREAM: 6277: openshift: Fix OCPBUGS-28200 [release-4.14] OCPBUGS-28200: UPSTREAM: 6277: openshift: Fix OCPBUGS-28200 Jan 31, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 31, 2024
@gcs278
Copy link
Author

gcs278 commented Jan 31, 2024

/assign @Miciah

@Miciah
Copy link

Miciah commented Jan 31, 2024

https://patch-diff.githubusercontent.com/raw/openshift/coredns/pull/112.patch and https://patch-diff.githubusercontent.com/raw/openshift/coredns/pull/114.patch are identical, so the approvals in #112 (comment) carry over.
/approve
/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Jan 31, 2024
@Miciah
Copy link

Miciah commented Jan 31, 2024

/approve

Copy link

openshift-ci bot commented Jan 31, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2024
@melvinjoseph86
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 1, 2024
@melvinjoseph86
Copy link

/retest

@melvinjoseph86
Copy link

Tested this PR with cluster bot.
/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 1, 2024
@gcs278
Copy link
Author

gcs278 commented Feb 1, 2024

/retest

@Miciah
Copy link

Miciah commented Feb 1, 2024

/skip

@Miciah
Copy link

Miciah commented Feb 1, 2024

Tide is showing that e2e-gcp-serial was run for #112 and the master branch, but this is #114 and the release-4.14 branch. Something is really broken here. Let's try overriding the bogus test...
/override e2e-gcp-serial

@Miciah
Copy link

Miciah commented Feb 1, 2024

/override ci/prow/e2e-gcp-serial

Copy link

openshift-ci bot commented Feb 1, 2024

@Miciah: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • e2e-gcp-serial

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-aws-ovn
  • ci/prow/e2e-aws-ovn-upgrade
  • ci/prow/e2e-gcp-sdn-serial
  • ci/prow/e2e-gcp-serial
  • ci/prow/e2e-metal-ipi-ovn
  • ci/prow/images
  • ci/prow/unit
  • pull-ci-openshift-coredns-master-e2e-aws-ovn
  • pull-ci-openshift-coredns-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-coredns-master-e2e-gcp-serial
  • pull-ci-openshift-coredns-master-e2e-metal-ipi-ovn
  • pull-ci-openshift-coredns-master-images
  • pull-ci-openshift-coredns-master-unit
  • pull-ci-openshift-coredns-release-4.12-e2e-gcp-sdn-serial
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

Tide is showing that e2e-gcp-serial was run for #112 and the master branch, but this is #114 and the release-4.14 branch. Something is really broken here. Let's try overriding the bogus test...
/override e2e-gcp-serial

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.

Copy link

openshift-ci bot commented Feb 1, 2024

@Miciah: Overrode contexts on behalf of Miciah: ci/prow/e2e-gcp-serial

In response to this:

/override ci/prow/e2e-gcp-serial

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.

Copy link

openshift-ci bot commented Feb 1, 2024

@gcs278: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-metal-ipi-ovn 7a0f883 link false /test e2e-metal-ipi-ovn

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 7d3fa77 into openshift:release-4.14 Feb 1, 2024
7 of 8 checks passed
@openshift-ci-robot
Copy link

@gcs278: Jira Issue OCPBUGS-28200: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-28200 has been moved to the MODIFIED state.

In response to this:

4.14 Cherry-Pick of coredns#6277 which fixes OCPBUGS-28200 by adding logic that more gracefully handles overflow errors by setting the Truncated Bit and clearing the response. This indicates to DNS clients to retry with TCP, whereas previously they would have always gotten a SERVFAIL.

This becomes more important/exposed with CoreDNS 1.10.1 (OCP 4.13) onwards, given the changes introduced by coredns#5671. This modification only uses EDNS on the upstream DNS request when the client query used EDNS. It appears that certain DNS resolvers may not handle non-EDNS queries in a compliant manner.

Cherry-Pick Merge Conflict:

CONFLICT (modify/delete): plugin/pkg/proxy/proxy_test.go deleted in HEAD and modified in 37a9afe69 (UPSTREAM: 6277: openshift: Fix OCPBUGS-27397).  Version 37a9afe69 (UPSTREAM: 6277: openshift: Fix OCPBUGS-27397) of plugin/pkg/proxy/proxy_test.go left in tree.
  • plugin/pkg/proxy directory doesn't exist in release-4.14 due to refactoring, so I placed the unit tests in plugin/forward/proxy_test.go
  • Required some refactoring due to function signature changes and other refactoring

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build coredns-container-v4.14.0-202402011639.p0.g7d3fa77.assembly.stream for distgit coredns.
All builds following this will include this PR.

@openshift-merge-robot
Copy link

Fix included in accepted release 4.14.0-0.nightly-2024-02-02-015353

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants