Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Destroy model silently fails with external storage #3659

Closed
cassiocassio opened this issue May 18, 2018 · 2 comments
Closed

Destroy model silently fails with external storage #3659

cassiocassio opened this issue May 18, 2018 · 2 comments
Assignees
Labels
Milestone

Comments

@cassiocassio
Copy link

cassiocassio commented May 18, 2018

Destroying a model in the GUI silently fails

Clicking on the < trash> icon:
screen shot 2018-05-18 at 11 03 27

... leads to the confirm dialog:

screen shot 2018-05-18 at 11 03 24

Clicking

--

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)

  1. Improve the error language for the juju CLI

'ERROR cannot destroy model: use --destroy-storage option to force.

  1. If attached storage is also destroyed, make it clear in the dialog.

destroy all

@cassiocassio cassiocassio self-assigned this May 18, 2018
@hatched hatched changed the title Destroy model silently fails Destroy model silently fails with external storage May 18, 2018
@frankban
Copy link
Member

Isn't this also a problem in current API client system always selecting most recent facade version?

@frankban frankban added this to the unbelievable uhura milestone Jul 30, 2018
@frankban frankban added the bug label Jul 30, 2018
@hatched
Copy link
Contributor

hatched commented Jul 30, 2018

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

3 participants