juju destroy-controller doesn't properly remove models
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
I ran `juju destroy-controller cdkkf --yes --destroy-
The following errors were encountered during destroying the model.
You can fix the problem causing the errors and run destroy-model again.
Resource Id Message
Volume 0 destroying volume: getting volume pvc-5a58e6b6-
1 destroying volume: getting volume pvc-4c464c80-
2 destroying volume: getting volume pvc-dcb44512-
It looks like it's attempting to talk to the Charmed Kubernetes cluster to tear down the Kubeflow model, but that entire cluster was destroyed first, and Juju doesn't know that one model is layered on top of the other.
Is there a way to inform Juju that two models are layered and should be destroyed in a certain order?
We don't model dependencies between models to allow an ordered destroy to occur. But it's something we need to look at doing to support scenarios such as the one in this bug. For now, the best approach is to destroy any models based on a CDK cluster hosted by the some controller first.