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

Reboot server after un-allocate #1285

Open
aarnaud opened this issue Jan 18, 2024 · 4 comments
Open

Reboot server after un-allocate #1285

aarnaud opened this issue Jan 18, 2024 · 4 comments

Comments

@aarnaud
Copy link
Contributor

aarnaud commented Jan 18, 2024

After deletion of cluster, servers are un-allocated in CAPI but their are never rebooted, so the k8s still running.

NAME                                   HOSTNAME        BMC IP   ACCEPTED   CORDONED   ALLOCATED   CLEAN   POWER   AGE
0e559c4c-3278-11b2-xxxx                lab-1                    true                  false       false   on      3h36m
40f85200-e0bc-11e9-xxxx                lab-2                    true                  false       false   on      4h4m
415c4bf2-db1a-c6e3-xxxx                lab-3                    true                  false       false   on      4h4m

So the Clean status stay at False

I saw this issue #146 but it seem the reboot is missing.

@smira
Copy link
Member

smira commented Jan 22, 2024

Sidero Metal requires IPMI to handle reboot/reset/wipe of the machines.

@aarnaud
Copy link
Contributor Author

aarnaud commented Jan 22, 2024

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.
If yes, I can try to make a PR

@aarnaud
Copy link
Contributor Author

aarnaud commented Jan 31, 2024

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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
@aarnaud
Copy link
Contributor Author

aarnaud commented Feb 8, 2024

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 <[email protected]>
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 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants