heads up! upgrade-juju from v1.10 must go via v1.12

roger peppe roger.peppe at canonical.com
Thu Aug 1 16:49:35 UTC 2013

I have just merged a branch
that removes some code that was in place to deal with 1.10-related

In particular 1.10 unit agents did not have information about
how to connect to the API, and LXC was not installed by

The code in question still lives in 1.12, so this means that
if you want to upgrade from 1.10 to trunk tip (or 1.14 when
it happens), you'll need to go via 1.12.

Currently version 1.12 is not available in the ec2
public tools bucket, so you'll need to download
it, build it and upgrade to it explictly:

$ wget https://launchpad.net/juju-core/1.12/1.12.0/+download/juju-core_1.12.0-1.tar.gz
$ tar xzf juju-core_1.12.0-1.tar.gz
$ cd juju-core_1.12.0
$ export GOPATH=`pwd`
$ go install launchpad/juju-core/cmd/juju...
$ juju upgrade-juju --upload-tools
# Repeat the following status command until all
# machines and units report agent-version=1.12.0
$ juju status

Now you should have a juju environment that can
upgrade to the latest juju version OK.

I hope this seems reasonable (and I hope that almost
everyone keen enough to be running 1.10 will
have upgrade to 1.12 immediately it's available
anyway :-])


More information about the Juju-dev mailing list