Bootstrap prefers .jenv over environments.yaml
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
I am using the manual provider, so .jenv files are left behind.
When I start a new instance, I get a new IP and write it into the environments.yaml as the bootstrap-host (see also bug #1282217).
When I bootstrap, juju ignores the value I deliberately changed in environments.yaml, and instead uses the stale value from the .jenv
This is a bug because juju is ignoring the user's explicit choice to change the value in environments.yaml, where users are supposed to change the value. Users should not have to hand-hack the .jenv or delete it for a new environment to use the values in environments.yaml.
It is a regression because in previous versions, bootstrap always used the values from environments.yaml
Related branches
- Juju Engineering: Pending requested
-
Diff: 161 lines (+48/-3)9 files modifiedCONTRIBUTING (+1/-1)
agent/mongo/mongo.go (+1/-1)
cmd/juju/bootstrap.go (+2/-1)
cmd/juju/bootstrap_test.go (+23/-0)
environs/configstore/disk.go (+5/-0)
environs/configstore/disk_test.go (+1/-0)
environs/configstore/interface.go (+4/-0)
environs/configstore/mem.go (+5/-0)
environs/configstore/mem_test.go (+6/-0)
Changed in juju-core: | |
importance: | Low → High |
milestone: | none → 1.17.5 |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
assignee: | nobody → Michael Foord (mfoord) |
Changed in juju-core: | |
status: | Fix Committed → Triaged |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
milestone: | 1.17.5 → 1.18.0 |
Changed in juju-core: | |
milestone: | 1.20.0 → 2.0 |
Changed in juju-core: | |
assignee: | Michael Foord (mfoord) → nobody |
Changed in juju-core: | |
importance: | High → Medium |
Changed in juju-core: | |
milestone: | none → 1.21-alpha3 |
Changed in juju-core: | |
milestone: | 1.21-alpha3 → none |
tags: | added: config |
tags: | added: destroy-environment |
So these are left behind because we aren't using "juju destroy- environment" to clean it up?