destroy-model --force broken if a model has configured a bad(inaccessible) vault secret backend

Bug #1997204 reported by Yang Kelvin Liu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Medium
Unassigned

Bug Description

machine-0: 17:15:29 ERROR juju.worker.dependency "undertaker" manifold worker returned unexpected error: cannot remove model: cleaning model from secrets provider: Get "http://10.140.116.236:8200/v1/sys/policies/acl?list=true": dial tcp 10.140.116.236:8200: connect: no route to host

The above error should be ignored if --force is provided.
`juju destroy-model -y --debug --force --destroy-storage model-secrets-vault`

a bad secret backend configuration could cause the model to teardown with --force broken.

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 3.0.1
milestone: 3.0.1 → 3.0.2
milestone: 3.0.2 → 3.0.3
Changed in juju:
milestone: 3.0.3 → 3.0.4
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.