What happened:
Without MHC for MachineDeployment, when I stopped the compute instance, machine object in 'failed' status as expected and worker node in "NotReady" status as expected. While after restarting the compute instance, the worker node back "Ready" status, while machine object still in "failed" status, capoci log showing the ocimachine already 'Active'
What you expected to happen:
machine object should be in "Running" status
How to reproduce it (as minimally and precisely as possible):
deploy a MD without MHC, and stop the worker node, after the machine object turned to "failed", then start the worker node.
Anything else we need to know?:
Environment:
CAPOCI version: v0.11.2
Cluster-API version (use clusterctl version): v1.4.1
What happened: Without MHC for MachineDeployment, when I stopped the compute instance, machine object in 'failed' status as expected and worker node in "NotReady" status as expected. While after restarting the compute instance, the worker node back "Ready" status, while machine object still in "failed" status, capoci log showing the ocimachine already 'Active' What you expected to happen: machine object should be in "Running" status How to reproduce it (as minimally and precisely as possible): deploy a MD without MHC, and stop the worker node, after the machine object turned to "failed", then start the worker node. Anything else we need to know?:
Environment:
clusterctl version): v1.4.1kubectl version): 1.24.8docker info):/etc/os-release):