GetMachineStatus prevents machine deletion in case of Unitialised error code

[rishabh-11]

How to categorize this issue?

/area performance
/area robustness
/kind bug
/priority 1

What happened:
With #898, we introduced InitializeMachine in the driver API. There is an edge case here where an initialized machine can cause its deletion to be stuck (See landscape-issues 147). This happens because of the triggerDeletionFlow calls GetMachineStatus in getVMStatus stage. (See

machine-controller-manager/pkg/util/provider/machinecontroller/machine_util.go

Line 916 in 0a6589d

func (c *controller) getVMStatus(ctx context.Context, getMachineStatusRequest *driver.GetMachineStatusRequest) (machineutils.RetryPeriod, error) {

). The error handling of Unitialized error code is not done here causing the deletion to get stuck.

What you expected to happen:
The deletion of an initialized machine should not get stuck.

Anything else we need to know?: