Automated cherry pick of #112693: Fixed (CVE-2022-27664) Bump golang.org/x/net to

[aimuz]

Cherry pick of #112693 on release-1.24.

#112693: Fixed (CVE-2022-27664) Bump golang.org/x/net to

For details on the cherry pick process, see the cherry pick requests page.

Updates golang.org/x/net to v0.1.1-0.20221027164007-c63010009c80 to resolve CVE-2022-27664

[k8s-ci-robot]

Hi @aimuz. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[aimuz]

/kind bug

[liggitt]

oh, that's irritating... the golang.org/x/sys update requires modifying go.mod to go1.18

vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)

that's why the analysis is failing... builds and unit tests also fail

I guess I'll pick #109440 to release-1.24 separately, then this should work

[dims]

I guess I'll pick #109440 to release-1.24 separately, then this should work

Sounds good @liggitt

[liggitt]

sorry for the conflicts, but if you replay the version bump on latest release-1.24, the verification errors should be resolved now

[aimuz]

Yes, he had to change to 1.18, can the 1.23 branch be changed?

[liggitt]

Not yet, 1.24 was already building with go1.18. Getting 1.23 onto go1.18 is more involved (see #113416)

[aimuz]

/retest

[k8s-ci-robot]

@aimuz: 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
pull-kubernetes-e2e-capz-windows-containerd-1-24	4e2d7a0	link	false	/test pull-kubernetes-e2e-capz-windows-containerd-1-24

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[aimuz]

pull-kubernetes-e2e-capz-windows-containerd-1-24 testing behavior is curiously dependent on go 1.19

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/113459/pull-kubernetes-e2e-capz-windows-containerd-1-24/1592715586062782464#1:build-log.txt%3A64

[liggitt]

that job's config was just modified in kubernetes/test-infra#27971 (comment), asked about it there

[liggitt]

/skip
/lgtm
/approve

[liggitt]

cc @kubernetes/release-managers

[cpanato]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aimuz, cpanato, liggitt

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 [liggitt]
• staging/src/k8s.io/api/OWNERS [liggitt]
• staging/src/k8s.io/legacy-cloud-providers/OWNERS [liggitt]

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