sidero icon indicating copy to clipboard operation
sidero copied to clipboard

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

Open blackliner opened this issue 1 year ago • 0 comments

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 avatar Jan 22 '24 04:01 blackliner