Skip to content

[release-4.12] OCPBUGS-15251: Add protocolStrategy for upstreams in dnses.operator.openshift.io#1502

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.12from
openshift-cherrypick-robot:cherry-pick-1429-to-release-4.12
Aug 16, 2023
Merged

[release-4.12] OCPBUGS-15251: Add protocolStrategy for upstreams in dnses.operator.openshift.io#1502
openshift-merge-robot merged 1 commit intoopenshift:release-4.12from
openshift-cherrypick-robot:cherry-pick-1429-to-release-4.12

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #1429

/assign gcs278

…enshift.io

protocolStrategy adds the ability to configure the force_tcp CoreDNS
Corefile configuration for upstreams, which forces TCP for all upstream
DNS requests. This is to resolve issues regarding problematic DNS
upstreams as well as a potential UDP reliability problems.
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-6829 has been cloned as Jira Issue OCPBUGS-15251. Will retitle bug to link to clone.
/retitle [release-4.12] OCPBUGS-15251: Add protocolStrategy for upstreams in dnses.operator.openshift.io

Details

In response to this:

This is an automated cherry-pick of #1429

/assign gcs278

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 21, 2023

Hello @openshift-cherrypick-robot! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci Bot changed the title [release-4.12] OCPBUGS-6829: Add protocolStrategy for upstreams in dnses.operator.openshift.io [release-4.12] OCPBUGS-15251: Add protocolStrategy for upstreams in dnses.operator.openshift.io Jun 21, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 21, 2023
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-15251, which is invalid:

  • expected dependent Jira Issue OCPBUGS-6829 to target a version in 4.13.0, 4.13.z, but it targets "4.14.0" instead

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

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

Details

In response to this:

This is an automated cherry-pick of #1429

/assign gcs278

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 openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 21, 2023
@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Jun 21, 2023

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@gcs278: This pull request references Jira Issue OCPBUGS-15251, which is invalid:

  • expected dependent Jira Issue OCPBUGS-15225 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is POST instead
  • expected dependent Jira Issue OCPBUGS-6829 to target a version in 4.13.0, 4.13.z, but it targets "4.14.0" instead

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

Details

In response to this:

/jira 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.

@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Jun 21, 2023

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@gcs278: This pull request references Jira Issue OCPBUGS-15251, which is invalid:

  • expected dependent Jira Issue OCPBUGS-15225 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is POST instead

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

Details

In response to this:

/jira 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 openshift-ci Bot requested review from knobunc and soltysh June 21, 2023 13:30
@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Jun 21, 2023

Slack Discussion about backporting

@candita
Copy link
Copy Markdown
Contributor

candita commented Jun 21, 2023

/assign
cc @Miciah if you're already involved

@candita
Copy link
Copy Markdown
Contributor

candita commented Jun 21, 2023

@gcs278 can you investigate the verify-client-go failure?

@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Jun 21, 2023

@candita will look into it.
Let me try one more time
/test verify-client-go

@candita
Copy link
Copy Markdown
Contributor

candita commented Jun 22, 2023

Backport looks correct, and justification for backport from Slack thread has been approved by team lead, PM, and manager.
/lgtm

@candita
Copy link
Copy Markdown
Contributor

candita commented Jun 22, 2023

@gcs278 you'll need to check in to the verify-client-go failure. It may be that this can't be backported to 4.12 after all.

  • mv ./vendor/k8s.io/code-generator/generate-groups.sh.orig ./vendor/k8s.io/code-generator/generate-groups.sh
    insights/applyconfigurations/insights/v1alpha1/datagather.go:6:2: cannot find package "github.com/openshift/client-go/vendor/github.com/openshift/api/insights/v1alpha1" in:
    /go/src/github.com/openshift/client-go/vendor/github.com/openshift/api/insights/v1alpha1
    monitoring/applyconfigurations/monitoring/v1/alertingrule.go:6:2: cannot find package "github.com/openshift/client-go/vendor/github.com/openshift/api/monitoring/v1" in:
    /go/src/github.com/openshift/client-go/vendor/github.com/openshift/api/monitoring/v1

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 22, 2023
@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Jun 23, 2023

I spent sometime investigating, but it doesn't look like it's a failure that is specific to this PR, but more of a repo-level code generation issue. I asked forum-api-review here: https://redhat-internal.slack.com/archives/CE4L0F143/p1687540934599509

@candita
Copy link
Copy Markdown
Contributor

candita commented Jul 13, 2023

@gcs278 can you follow up on the slack thread regarding verify-client-go?

@melvinjoseph86
Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jul 17, 2023
@openshift-ci-robot
Copy link
Copy Markdown

@melvinjoseph86: This pull request references Jira Issue OCPBUGS-15251, which is valid. The bug has been moved to the POST state.

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

Requesting review from QA contact:
/cc @melvinjoseph86

Details

In response to this:

/jira 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 removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 17, 2023
@openshift-ci openshift-ci Bot requested a review from melvinjoseph86 July 17, 2023 04:23
@Miciah
Copy link
Copy Markdown
Contributor

Miciah commented Jul 21, 2023

/test verify-client-go

@Miciah
Copy link
Copy Markdown
Contributor

Miciah commented Jul 24, 2023

I've filed OCPBUGS-16720 for the verify-client-go failures.

@JoelSpeed
Copy link
Copy Markdown
Contributor

/test verify-client-go

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 26, 2023

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Jul 26, 2023

@JoelSpeed thanks for following up with the verify-client-go fixes.

Could I get you to apply approve and backport-risk-assessed to this PR?

@JoelSpeed
Copy link
Copy Markdown
Contributor

JoelSpeed commented Jul 26, 2023

Do we have staff eng approval for backporting this? Typically backporting features into z streams has strict requirements, especially for going back a couple of releases

@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Jul 26, 2023

Do we have staff eng approval for backporting this? Typically backporting features into z streams has strict requirements, especially for going back a couple of releases

@JoelSpeed I was slightly mistaken. For the 4.13 backport, @soltysh approved it, looks like he is on vacation though. PM has approved it in this Slack Thread.

Copy link
Copy Markdown
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 4, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 4, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: candita, openshift-cherrypick-robot, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Aug 4, 2023
@melvinjoseph86
Copy link
Copy Markdown

/label cherry-pick-approved

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 4, 2023

@melvinjoseph86: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]

Details

In response to this:

/label cherry-pick-approved

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.

@melvinjoseph86
Copy link
Copy Markdown

@gangwgr @wangke19 @xingxingxia Kindly help adding cherry-pick-approved label

@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Aug 14, 2023

@gangwgr @wangke19 @xingxingxia Kindly help adding cherry-pick-approved label

Friendly reminder

@xingxingxia
Copy link
Copy Markdown

/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 Aug 16, 2023
@openshift-merge-robot openshift-merge-robot merged commit b8dd6b6 into openshift:release-4.12 Aug 16, 2023
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-15251: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

Details

In response to this:

This is an automated cherry-pick of #1429

/assign gcs278

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
Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.12.0-0.nightly-2023-09-08-181253

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-important Referenced Jira bug's severity is important 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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.