vSphere IPI - MachineWithNoRunningPhase - Force retry possible?

[danielchristianschroeter]

After encountering vSphere permission issues, the following error is now being displayed:
MachineWithNoRunningPhase
The machine has been without a Running or Deleting phase for more than 60 minutes. The machine may not have been provisioned properly from the infrastructure provider, or it might have issues with CertificateSigningRequests being approved.

Although vSphere permissions have been restored, the machines provided are still stuck in the "Failed" phase. Is there a way to trigger a retry process?

Example node machine output:

oc get machine -n openshift-machine-api okd-01-zvldl-infra-g6tmm -o yaml
apiVersion: machine.openshift.io/v1beta1
kind: Machine
metadata:
  annotations:
    machine.openshift.io/instance-state: Unknown
  creationTimestamp: "2022-09-21T09:28:21Z"
  finalizers:
  - machine.machine.openshift.io
  generateName: okd-01-zvldl-infra-
  generation: 2
  labels:
    machine.openshift.io/cluster-api-cluster: okd-01-zvldl
    machine.openshift.io/cluster-api-machine-role: infra
    machine.openshift.io/cluster-api-machine-type: infra
    machine.openshift.io/cluster-api-machineset: okd-01-zvldl-infra
    machine.openshift.io/region: ""
    machine.openshift.io/zone: ""
  name: okd-01-zvldl-infra-g6tmm
  namespace: openshift-machine-api
  ownerReferences:
  - apiVersion: machine.openshift.io/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: MachineSet
    name: okd-01-zvldl-infra
    uid: 848d2c95-a06c-4069-a955-2c410ab06c2e
  resourceVersion: "517019307"
  uid: 562a135c-5c84-4c2d-b41a-d414928fa80a
spec:
  lifecycleHooks: {}
  metadata:
    labels:
      node-role.kubernetes.io: infra
      node-role.kubernetes.io/infra: ""
  providerID: vsphere://420ab75a-5e33-ae11-b02a-5c86c4900812
  providerSpec:
    value:
      apiVersion: vsphereprovider.openshift.io/v1beta1
      credentialsSecret:
        name: vsphere-cloud-credentials
      diskGiB: 256
      kind: VSphereMachineProviderSpec
      memoryMiB: 65536
      metadata:
        creationTimestamp: null
      network:
        devices:
        - networkName: k8s-test
      numCPUs: 8
      numCoresPerSocket: 1
      snapshot: ""
      template: okd-01-zvldl-rhcos
      userDataSecret:
        name: worker-user-data
      workspace:
        datacenter: xx
        datastore: xxx
        folder: /xx/test
        resourcePool: /xx/xx-Test
        server: xxx.xx
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/infra
    value: reserved
  - effect: NoExecute
    key: node-role.kubernetes.io/infra
    value: reserved
status:
  addresses:
  - address: xx.1.233.xx
    type: InternalIP
  - address: xx.254.xx.2
    type: InternalIP
  - address: xx::66bf:xx:476f:c0b7
    type: InternalIP
  - address: okd-01-zvldl-infra-g6tmm
    type: InternalDNS
  conditions:
  - lastTransitionTime: "2022-09-21T09:28:21Z"
    status: "True"
    type: Drainable
  - lastTransitionTime: "2024-02-27T11:23:45Z"
    message: Instance not found on provider
    reason: InstanceMissing
    severity: Warning
    status: "False"
    type: InstanceExists
  - lastTransitionTime: "2022-09-21T09:28:21Z"
    status: "True"
    type: Terminable
  errorMessage: can't find created instance
  lastUpdated: "2024-02-27T14:12:32Z"
  nodeRef:
    kind: Node
    name: okd-01-zvldl-infra-g6tmm
    uid: faf1164f-e253-44bf-a687-22845af346b7
  phase: Failed
  providerStatus:
    conditions:
    - lastTransitionTime: "2022-09-21T09:28:23Z"
      message: Machine successfully created
      reason: MachineCreationSucceeded
      status: "True"
      type: MachineCreation
    instanceId: 420ab75a-5e33-ae11-b02a-5c86c4900812
    instanceState: Unknown
    taskRef: task-1161003