"upload-tools strikes back" cannot upgrade with streams
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
High
|
Unassigned |
Bug Description
Just as upgrades were broken in juju 1 when users used upload tools. Juju 2 users are broken by the juju clients implicit use of devel streams. The controller is misconfigured and cannot upgrade.
$ juju version
2.0-rc2-
juju bootstrap curtis-rackspace rackspace/iad
...Fetching Juju agent version 2.0-rc2 for amd64...
$ juju model-config -m controller agent-stream
released
^ No is it not! the agent is only in devel stream, Logs also show the agent from
https:/
$ juju upgrade-juju -m controller
no upgrades available
WORK AROUND
Tell the juju controller what juju client did
$ juju model-config -m controller agent-stream=devel
$ juju upgrade-juju -m controller
started upgrade to 2.0-rc3
$ juju upgrade-juju -m default
started upgrade to 2.0-rc3
Changed in juju: | |
assignee: | nobody → Alexis Bruemmer (alexis-bruemmer) |
description: | updated |
Changed in juju: | |
status: | Triaged → Incomplete |
milestone: | 2.0.0 → none |
Changed in juju: | |
assignee: | Alexis Bruemmer (alexis-bruemmer) → nobody |
agent-stream, unless set via --config, will default to "released". This is independent of what juju version the agent binaries are. It's always been this way. The idea is that if you want juju to search for a devel agent, you need to --config agent-stream=devel. The work around described in the bug report is actually what the required behaviour is - juju is working as designed. This allows the user to prevent juju from accidentally upgrading to a devel agent when the user wants juju to only look for released agents.