destroy-environment --force leaves a jenv lying around
Bug #1402696 reported by
Aaron Bentley
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Invalid
|
Medium
|
Unassigned | ||
| 1.23 |
Won't Fix
|
Medium
|
Unassigned | ||
| 1.25 |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
When destroy-environment --force works, it deletes the .jenv. When it reports that the environment isn't bootstrapped, it doesn't. A user who uses --force wants a clean system. It should always delete the .jenv, so that subsequent bootstraps are not polluted by it.
Revision history for this message
| Menno Finlay-Smits (menno.smits) wrote | #1 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #2 |
| Changed in juju-core: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
I've seen this too but perhaps not consistently. It seems that sometimes the jenv is cleaned up, sometimes it isn't.