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

feat/bug: deleting a cluster doesn't reset non-IPMI servers #1294

Open
blackliner opened this issue Jan 22, 2024 · 0 comments
Open

feat/bug: deleting a cluster doesn't reset non-IPMI servers #1294

blackliner opened this issue Jan 22, 2024 · 0 comments

Comments

@blackliner
Copy link

blackliner commented Jan 22, 2024

I deleted the Clusters resource, and expected that:

  • ✅ all Serverbindings were removed
  • ✅ all Servers were marked as Allocated = false
  • ✅ all IPMI capable servers were restarted, wiped and shut down
  • ❌ all non-IPMI capable servers were restarted, wiped and left in an endless boot cycle
    • instead, the servers were left as they were, completely intact and Talos just stayed in Running mode
    • these 3 servers are proxmox VMs

In the screenshot below one can observe:

  • admin@sidero-metal being the management cluster
  • admin@cluster-bravo being the workload cluster
  • metal04 being the IPMI capable server, reset, wiped, and shutdown (although it shows as Power == on, the server was cycled throug IPMI and then shut down)
  • node talos-yop-i9c representing metal04, not being removed from the cluster, and stuck as unavailable
  • all other 3 control plane nodes still around and healthy, accessible and not really influenced by the fact that the cluster was deleted
  • all 4 previously existing Serverbindings were removed
    image
@blackliner 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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant