-
Notifications
You must be signed in to change notification settings - Fork 180
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
[1.22] Fix CVE-2022-41723 by bumping golang.org/x/net to 0.8.0 #754
Conversation
Hi @wyike. 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 Once the patch is verified, the new status will be reflected by the 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. |
/assign @lubronzhan |
/ok-to-test |
/ok-to-test |
Hi @XudongLiuHarold @lubronzhan do you know why tests are not launched? Any runner issue or something? |
/test ? |
@wyike: The following commands are available to trigger required jobs:
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 kubernetes/test-infra repository. |
/test pull-cloud-provider-vsphere-unit-test |
@XudongLiuHarold: The specified target(s) for
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 kubernetes/test-infra repository. |
/test ? |
@wyike: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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 kubernetes/test-infra repository. |
/test all |
The test image gcr.io/k8s-staging-test-infra/kubekins-e2e:v20230727-ea685f8747-1.25 is using golang 1.20 Some of UT in release-1.22, release-1.23, release-1.24 can pass with golang 1.19 (tested locally) while golang 1.20 not:
Something is changed between golang/govmomi versions. To have the UT be compatible with golang 1.20:
Also from #736,, I did believe golang1.20 is not compatible with releases with govmomi lower than 0.36 (i.e. release-1.26 ~1.22). Hi @lubronzhan do we consider to run tests on 1.26-minus with golang 1.19 version image? Will it be more reasonable? I see for release 1.26 and earlier releases, actually the golang version for vsphere capi is not higher than 1.19.
|
Ok, I thought |
/retest |
@wyike: The following tests failed, say
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. |
1.22 doesn't have e2e script setup. e2e-test is expected to fail. |
Ok we can merge without the e2e |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lubronzhan, wyike 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 |
What this PR does / why we need it:
CVE fix CVE-2022-41723
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note: