Controller doesn't use tools uploaded with juju bootstrap --upload-tools
Bug #1605050 reported by
Menno Finlay-Smits
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Tim Penhey |
Bug Description
When testing a customised version of Juju 2.0-beta12 and I bootstrapped like this:
juju bootstrap foo lxd --upload-tools --auto-upgrade false
On inspecting the logs I found that after the controller had come up it had "upgraded" to the officially released 2.0-beta12 from the devel streams. This is very surprising and is almost certainly a bug. When --upload-tools is used it's those tools that should be used.
Changed in juju-core: | |
status: | New → Triaged |
description: | updated |
Changed in juju-core: | |
milestone: | 2.0-beta13 → 2.0-beta14 |
Changed in juju-core: | |
assignee: | nobody → Tim Penhey (thumper) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta14 → none |
milestone: | none → 2.0-beta14 |
To post a comment you must log in.
We have an environment where we are using a patched juju until the proposed fix for lp1602716 is merged, and this is making us stick with beta11.