upgrade-juju --upload-tools, using 1.20.11, from 1.18.4 upgraded to 1.19.4 instead
Bug #1392810 reported by
JuanJo Ciarlante
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Steps:
#1 Original state: stock trusty install with 1.18.4
#2 From ppa:juju/stable, installed 1.20.11-
#3 ran:
juju upgrade-juju --upload-tools --version=1.20.11
#4 Result: 1.19.4 got deployed, machine-0.log showing
http://
tags: | added: canonical-bootstack canonical-is |
summary: |
- upgrade-juju from 1.18.4 upgraded to 1.19.4 + upgrade-juju --upload-tools, using 1.20.11, from 1.18.4 upgraded to + 1.19.4 instead |
Changed in juju-core: | |
milestone: | 1.22-alpha1 → 1.23 |
Changed in juju-core: | |
milestone: | 1.23 → 1.24-alpha1 |
Changed in juju-core: | |
milestone: | 1.24-alpha1 → 1.25.0 |
Changed in juju-core: | |
milestone: | 1.25.0 → none |
importance: | High → Medium |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
--upload-tools is evil. we have separated streams to ensure users cannot get a devel agent, but the developer hack of --upload-tools is designed to make something exist.
We cannot fix 1.18, but we need to ensure that 120 or 1.21 will never select something that isn't in streams without the user specifically demanding it.