[release-4.12] OCPBUGS-20753: update x/net to v0.17.0

[JacobTanenbaum]

No description provided.

[openshift-ci-robot]

@JacobTanenbaum: This pull request references Jira Issue OCPBUGS-20753, which is invalid:

• expected Jira Issue OCPBUGS-20753 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

In response to this:

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.

[JacobTanenbaum]

/jira refresh

[openshift-ci-robot]

@JacobTanenbaum: This pull request references Jira Issue OCPBUGS-20753, 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-20771 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-20771 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 @zhaozhanqi

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

[tssurya]

/retest

[danwinship]

look like you forgot to git add the changes? (this only modifies go.mod and go.sum)

[openshift-ci]

@JacobTanenbaum: all tests passed!

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.

[danwinship]

/lgtm
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, JacobTanenbaum

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:

• OWNERS [danwinship]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mffiedler]

/label cherry-pick-approved

[openshift-ci-robot]

@JacobTanenbaum: Jira Issue OCPBUGS-20753: All pull requests linked via external trackers have merged:

• openshift/sdn#615

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

In response to this:

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]

[ART PR BUILD NOTIFIER]

This PR has been included in build kube-proxy-container-v4.12.0-202402071338.p0.g9706f96.assembly.stream.el8 for distgit kube-proxy.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.12.0-0.nightly-2024-02-07-161700

[openshift-merge-robot]

Fix included in accepted release 4.12.0-0.nightly-2024-02-13-091433