You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2021. It is now read-only.
With @mhilton - Initially I thought this was when Juju controller requires destroyStorage to be true:
cassio@benbecula-2:~ $ juju destroy-model testk8s
WARNING! This command will destroy the "testk8s" model.
This includes all machines, applications, data and other resources.
Continue [y/N]? y
Destroying model
ERROR failed to destroy model "testk8s"
ERROR cannot destroy model: this Juju controller requires destroyStorage to be true
cassio@benbecula-2:~ $ juju destroy-model testk8s --destroy-storage
WARNING! This command will destroy the "testk8s" model.
This includes all machines, applications, data and other resources.
Continue [y/N]? y
Destroying model
but I fear also seems to be a problem in the general case. This needs further investigation.
Proposals: (in the case of the storage failure)
Improve the error language for the juju CLI
'ERROR cannot destroy model: use --destroy-storage option to force.
If attached storage is also destroyed, make it clear in the dialog.
The text was updated successfully, but these errors were encountered:
I think it's a combination of two things. We always select the latest facade version, and that we aren't sending that configuration option when destroying. We'll need to revisit this once the new jujulib stuff has been implemented.
Destroying a model in the GUI silently fails
Clicking on the < trash> icon:
... leads to the confirm dialog:
Clicking
--
With @mhilton - Initially I thought this was when Juju controller requires destroyStorage to be true:
but I fear also seems to be a problem in the general case. This needs further investigation.
Proposals: (in the case of the storage failure)
'ERROR cannot destroy model: use --destroy-storage option to force.
The text was updated successfully, but these errors were encountered: