manual provider: failed bootstrap leaves .jenv file behind

Bug #1282242 reported by Aaron Bentley
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Low
Unassigned

Bug Description

After bootstrap fails, (e.g. bug #1282235) a .jenv file is left behind. Running juju destroy-environment won't delete it.

$ juju destroy-environment manual
WARNING! this command will destroy the "manual" environment (type: manual)
This includes all machines, services, data and other resources.

Continue [y/N]? y
ERROR Get http://54.80.141.151:8040/provider-state: dial tcp 54.80.141.151:8040: connection refused
$ juju destroy-environment manual --force
WARNING! this command will destroy the "manual" environment (type: manual)
This includes all machines, services, data and other resources.

Continue [y/N]? y
ERROR exit status 1
abentley@speedy:~/canonical/ci-cd-scripts2$ ls manual-provider-home/environments
manual.jenv

Curtis Hovey (sinzui)
Changed in juju-core:
status: Triaged → Fix Released
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.