Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

machine status still showing 'failed' after restart a 'stopped' instance #337

Closed
QiangZhangO opened this issue Oct 12, 2023 · 0 comments · Fixed by #340
Closed

machine status still showing 'failed' after restart a 'stopped' instance #337

QiangZhangO opened this issue Oct 12, 2023 · 0 comments · Fixed by #340
Labels
bug Something isn't working

Comments

@QiangZhangO
Copy link

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
  • Kubernetes version (use kubectl version): 1.24.8
  • Docker version (use docker info):
  • OS (e.g. from /etc/os-release):
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant