Comment 0 for bug 1510944

As seen here:
http://reports.vapour.ws/releases/3230/job/xx-aws-upgrade-20-trusty-amd64/attempt/19

This test was performed with very small streams, containing just the source and target agents, but since the state-server was able to upgrade, it seems unlikely that the streams were at fault. Perhaps the small size revealed a timing issue.
ure
The stream releases file is here:
https://s3.amazonaws.com/temp-streams/xx-aws-upgrade-20-trusty-amd64/19/streams/v1/com.ubuntu.juju-released-tools.json

The machine log shows that the uniter contains "upgrade requested from 1.20.11-trusty-amd64 to 1.26-alpha1
... ERROR ... "upgrader": no matching tools available"

http://data.vapour.ws/juju-ci/products/version-3230/xx-aws-upgrade-20-trusty-amd64/build-19/machine-1.log.gz

This does not always happen; an earlier run with the 1.25 branch showed success:
http://juju-ci.vapour.ws/job/xx-aws-upgrade-20-trusty-amd64/15/