| 2016-10-07 20:52:12 |
Curtis Hovey |
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-xenial-amd64
juju bootstrap curtis-rackspace rackspace/iad
...Fetching Juju agent version 2.0-rc2 for amd64...
$ juju model-config -m controller agent-stream
released
^ Not is it not! the agent is only in devel stream, Logs also show the agent from
https://streams.canonical.com/juju/tools/agent/2.0-rc2/juju-2.0-rc2-xenial-amd64.tgz
$ 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 |
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-xenial-amd64
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://streams.canonical.com/juju/tools/agent/2.0-rc2/juju-2.0-rc2-xenial-amd64.tgz
$ 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 |
|
