[release-4.13] OCPBUGS-40929: update VPA golang.org/x/net for http rapid reset for CVE-2024-8421

[joelsmith]

go get golang.org/x/net@v0.23.0
go mod tidy
go mod vendor

[openshift-ci-robot]

@joelsmith: This pull request references Jira Issue OCPBUGS-40929, which is invalid:

• expected dependent Jira Issue OCPBUGS-40925 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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.

In response to this:

go get golang.org/x/net@v0.23.0
go mod tidy
go mod vendor

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.

[joelsmith]

I have no idea if the failing tests are expected to pass on this branch. We might need to flag/skip them.

/retest

[joelsmith]

/retest

[asahay19]

/label cherry-pick-approved

[openshift-ci]

@joelsmith: 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-azure-operator	3d1c67a	link	false	/test e2e-azure-operator

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

[joelsmith]

/retest-required

[jkyros]

That first e2e-azure-operator run went fine-ish until it failed on that cluster autoscaler test, it looks like it didn't even make it to the vpa tests.

   [TIMEDOUT] Managed cluster should when machineset has one replica [It] have ability to additively reconcile taints from machine to nodes [machines]
  /go/src/github.com/openshift/cluster-api-actuator-pkg/pkg/infra/infra.go:195

The other two look like it's the installer having problem with the install config and some azure user tag feature gates:

 baseDomain: ci.azure.devcluster.openshift.com
platform:
  azure:
    region: centralus
    userTags:
      expirationDate: 2024-09-10T13:35+00:00
    baseDomainResourceGroupName: os4-common
controlPlane:
  architecture: amd64
  name: master
  platform:
    azure:
      type: null
compute:
- architecture: amd64
  name: worker
  replicas: 3
  platform:
    azure:
      type: Standard_D4s_v3
level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: invalid "install-config.yaml" file: platform.azure.userTags: Forbidden: the TechPreviewNoUpgrade feature set must be enabled to use this field
Create manifests exit code: 3

I don't think we can really affect that either. And we didn't bump any Azure deps or anything so I'm reasonably sure we didn't specifically break Azure. (Plus the Azure test is not required)

Thanks for cranking through these Joel!

/lgtm

[joelsmith]

/approve
/label backport-risk-assessed
/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.z) matches configured target version for branch (4.13.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-40925 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-40925 targets the "4.14.z" version, which is one of the valid target versions: 4.14.0, 4.14.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (schoudha@redhat.com), skipping review request.

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

In response to this:

/approve
/label backport-risk-assessed
/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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelsmith

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:

• vertical-pod-autoscaler/OWNERS [joelsmith]

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

[openshift-ci-robot]

@joelsmith: Jira Issue OCPBUGS-40929: All pull requests linked via external trackers have merged:

• openshift/kubernetes-autoscaler#317

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

In response to this:

go get golang.org/x/net@v0.23.0
go mod tidy
go mod vendor

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]

Distgit: vertical-pod-autoscaler
This PR has been included in build ose-vertical-pod-autoscaler-container-v4.13.0-202409161537.p0.gc38cc4e.assembly.stream.el8.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: atomic-openshift-cluster-autoscaler
This PR has been included in build atomic-openshift-cluster-autoscaler-container-v4.13.0-202409161537.p0.gc38cc4e.assembly.stream.el8.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.13.0-0.nightly-2024-09-16-192737