-
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
Bump govmomi to 0.30.6 #738
Bump govmomi to 0.30.6 #738
Conversation
93de6f4
to
37c577b
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: HanFa, lubronzhan 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 |
Does this also need to be updated in kubernetes/kubernetes for go1.20? That is still using v0.30.0 (see kubernetes/kubernetes#114766 and backports) |
cc @wyike it should be needed |
@liggitt I think we'll have to bump and back-port. This issue didn't surface directly in our CI. We did a similar fix but in our tests: kubernetes/kubernetes@c31cc5e |
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com> Kubernetes-commit: fc6b19a4ba669da7a55f0c061f465fdfe4510720
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com> Kubernetes-commit: 7551decb3fe44014ce982d78a7bd3ab352332b30
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com> Kubernetes-commit: 0dc2f88f546a83ec7166f19c7cb37d8c70cdeeb7
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com> Kubernetes-commit: ecf1a9de9651053b285e909bfbf8e493080a6c5f
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com> Kubernetes-commit: ef63f36ff8297f47c9fe232836f0ed859f3ccf85
Bumping govmomi to include an error check fix needed to work with go1.20. We made this fix in the CI, but were reliant on the text matching of error strings, which is why it didn't catch the actual issue. This Fix in vmware/govmomi@b4eac19 PR to bump govmomi in cloud-provider-vsphere: kubernetes/cloud-provider-vsphere#738 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
What this PR does / why we need it:
Need govmomi fix vmware/govmomi#3174 for validating certificate's tlsthumbprint to work properly
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes ##736Special notes for your reviewer:
Release note: