🐛 vspherevm: don't requeue on deletenode when there is no ClusterCache connection

[chrischdi]

What this PR does / why we need it:

Makes the best-effort node-deletion to not cause infinite requeue when there is no connection to the workload cluster.

Bug was introduced in:

• 🌱 Replace CAPI's clustercache tracker by the new clustercache #3236

Note: this only affected pre-releases of v1.12 prior to this commit.

If kubeadm init failed, this would have lead to CAPV always requeue and never remove the finalizer. So deletion would have been stuck.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[chrischdi]

/cherry-pick release-1.12

[k8s-infra-cherrypick-robot]

@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.12 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.12

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.

[chrischdi]

/hold

[fabriziopandini]

Thanks for looking into this!
/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: a589b95af6007d1e9fdbc1afe9b79ad4a0b43c9a

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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 [fabriziopandini]

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

[chrischdi]

/hold cancel

[k8s-infra-cherrypick-robot]

@chrischdi: new pull request created: #3298

In response to this:

/cherry-pick release-1.12

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.