-
Notifications
You must be signed in to change notification settings - Fork 64
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
Reboot server after un-allocate #1285
Comments
Sidero Metal requires IPMI to handle reboot/reset/wipe of the machines. |
Is there a way to have software reboot with Talos API when IPMI isn't available ? because there is the Talos cert is in CAPI. |
I opened a discussion here about alternative if BMC can't be use: |
aarnaud
added a commit
to aarnaud/sidero
that referenced
this issue
Feb 8, 2024
…unallocated server all deleted machine will receive a reset call from talos client. Signed-off-by: Anthony ARNAUD <github@anthony-arnaud.fr>
aarnaud
added a commit
to aarnaud/sidero
that referenced
this issue
Feb 8, 2024
Ref: siderolabs#1294 siderolabs#1285 all deleted machine will receive a reset call from talos client. Signed-off-by: Anthony ARNAUD <github@anthony-arnaud.fr>
aarnaud
added a commit
to aarnaud/sidero
that referenced
this issue
Feb 8, 2024
Ref: siderolabs#1294 siderolabs#1285 all deleted machine will receive a reset call from talos client. Signed-off-by: Anthony ARNAUD <github@anthony-arnaud.fr>
aarnaud
added a commit
to aarnaud/sidero
that referenced
this issue
Feb 8, 2024
Ref: siderolabs#1294 siderolabs#1285 all deleted machine will receive a reset call from talos client. Signed-off-by: Anthony ARNAUD <github@anthony-arnaud.fr>
aarnaud
added a commit
to aarnaud/sidero
that referenced
this issue
Feb 8, 2024
Ref: siderolabs#1294 siderolabs#1285 all deleted machine will receive a reset call from talos client Signed-off-by: Anthony ARNAUD <github@anthony-arnaud.fr>
aarnaud
added a commit
to aarnaud/sidero
that referenced
this issue
Feb 8, 2024
Ref: siderolabs#1294 siderolabs#1285 all deleted machine will receive a reset call from talos client Signed-off-by: Anthony ARNAUD <github@anthony-arnaud.fr>
I push a draft PR here #1312 |
aarnaud
added a commit
to aarnaud/sidero
that referenced
this issue
Feb 8, 2024
Ref: siderolabs#1294 siderolabs#1285 all deleted machine will receive a reset call from talos client Signed-off-by: Anthony ARNAUD <github@anthony-arnaud.fr>
aarnaud
added a commit
to aarnaud/sidero
that referenced
this issue
Feb 8, 2024
Ref: siderolabs#1294 siderolabs#1285 all deleted machine will receive a reset call from talos client Signed-off-by: Anthony ARNAUD <github@anthony-arnaud.fr>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After deletion of cluster, servers are un-allocated in CAPI but their are never rebooted, so the k8s still running.
So the Clean status stay at False
I saw this issue #146 but it seem the reboot is missing.
The text was updated successfully, but these errors were encountered: