-
Notifications
You must be signed in to change notification settings - Fork 63
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
feat/bug: deleting a cluster doesn't reset non-IPMI servers #1294
Comments
blackliner
changed the title
bug: deleting a cluster doesn't reset servers
feat/bug: deleting a cluster doesn't reset non-IPMI servers
Jan 22, 2024
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
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
I deleted the
Clusters
resource, and expected that:Serverbindings
were removedServers
were marked asAllocated = false
Running
modeIn the screenshot below one can observe:
admin@sidero-metal
being the management clusteradmin@cluster-bravo
being the workload clustermetal04
being the IPMI capable server, reset, wiped, and shutdown (although it shows asPower == on
, the server was cycled throug IPMI and then shut down)talos-yop-i9c
representingmetal04
, not being removed from the cluster, and stuck as unavailableServerbindings
were removedThe text was updated successfully, but these errors were encountered: