E2E tests didn't catch govmomi connection error as cannot validate certificate

[zhanggbj]

What happened?

This is a error caught when running CAPV E2E tests but not in CPI E2E tests.

CPI: https://github.com/kubernetes/cloud-provider-vsphere/releases/tag/v1.32.0-beta.0

CAPV test: kubernetes-sigs/cluster-api-provider-vsphere#3250

E1107 18:20:17.894281       1 connection.go:181] Failed to create new client. err: Post "https://10.2.224.4:443/sdk": tls: failed to verify certificate: x509: cannot validate certificate for 10.2.224.4 because it doesn't contain any IP SANs
E1107 18:20:17.894401       1 connection.go:67] Failed to create govmomi client. err: Post "https://10.2.224.4:443/sdk": tls: failed to verify certificate: x509: cannot validate certificate for 10.2.224.4 because it doesn't contain any IP SANs
E1107 18:20:17.894422       1 connectionmanager.go:147] Cannot connect to vCenter with err: Post "https://10.2.224.4:443/sdk": tls: failed to verify certificate: x509: cannot validate certificate for 10.2.224.4 because it doesn't contain any IP SANs
E1107 18:20:18.903587       1 connection.go:181] Failed to create new client. err: Post "https://10.2.224.4:443/sdk": tls: failed to verify certificate: x509: cannot validate certificate for 10.2.224.4 because it doesn't contain any IP SANs
E1107 18:20:18.903635       1 connection.go:67] Failed to create govmomi client. err: Post "https://10.2.224.4:443/sdk": tls: failed to verify certificate: x509: cannot validate certificate for 10.2.224.4 because it doesn't contain any IP SANs
E1107 18:20:18.903649       1 connectionmanager.go:147] Cannot connect to vCenter with err: Post "https://10.2.224.4:443/sdk": tls: failed to verify certificate: x509: cannot validate certificate for 10.2.224.4 because it doesn't contain any IP SANs
E1107 18:20:19.911962       1 connection.go:181] Failed to create new client. err: Post "https://10.2.224.4:443/sdk": tls: failed to verify certificate: x509: cannot validate certificate for 10.2.224.4 because it doesn't contain any IP SANs

What did you expect to happen?

Investigate if CPI can catch this kind of error in tests and improve e2e tests.

How can we reproduce it (as minimally and precisely as possible)?

Run CAPV E2E test using
CPI: https://github.com/kubernetes/cloud-provider-vsphere/releases/tag/v1.32.0-beta.0

CAPV: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/releases/tag/v1.12.0-beta.0

Anything else we need to know (please consider providing level 4 or above logs of CPI)?

No response

Kubernetes version

$ kubectl version
# paste output here

1.32.0-beta.0

Cloud provider or hardware configuration

N/A

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Kernel (e.g. uname -a)

Install tools

Container runtime (CRI) and and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

Others

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[zhanggbj]

/remove-lifecycle stale