Installer overwrites existing juju environments.yaml file
Bug #1395197 reported by
Andreas Hasenack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| openstack-installer |
Fix Released
|
Critical
|
Adam Stokes | ||
Bug Description
If you have an existing ~/.juju/
Also, when calling sudo openstack-install -u, the ~/.juju directory and its contents are completely removed.
I think the installer should create its own juju directory and point JUJU_HOME at it. Then it can do whatever it wants with it.
Just keep in mind that removing JUJU_HOME will leave the machines up and running, and will leave the admin with no convenient way to manage them with juju anymore.
| description: | updated |
| description: | updated |
| Changed in cloud-installer: | |
| assignee: | nobody → Adam Stokes (adam-stokes) |
| milestone: | none → v0.22 |
| status: | New → In Progress |
Revision history for this message
| Mike McCracken (mikemc) wrote | #1 |
| Changed in cloud-installer: | |
| importance: | High → Critical |
| Changed in cloud-installer: | |
| status: | In Progress → Fix Committed |
| Changed in cloud-installer: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note - as of https:/
we do not remove ~/.juju anymore.
creating a separate JUJU_HOME is a good idea.