29 Nov
2022
29 Nov
'22
2:36 p.m.
Hi, Can you see what resource it is failing at with `openstack stack resource list -n5 <stack_id>`? You can also abandon the stack with `openstack stack abandon`. That will leave stray resources lying around though. Regards, Jake On 29/11/2022 2:09 am, wodel youchi wrote:
Hi,
I have a magnum cluster stack which contains errors in its constituents, some of the VMs (minions) that belong to that cluster do longer exist. When I try to delete the stack it fails, and I get
DELETE aborted (Task delete from ResourceGroup "kube_minions" [fddb3056-9b00-4665-b0d6-c3d3f176814b] Stack "testcluter01-puf45b6dxmrn" [d10af7f2-6ecd-442b-b1f9-140b79e58d13] Timed out)
Is there a way to force the deletion to proceed even with those errors?
Regards.