upgrade-juju broken in lxc

[Curtis Hovey]

The juju upgrade test from 1.16.6 to a.17.3 release candidate broken between revisions r2340 and r2341. I suspect r2340 "New unit upgrader back end" is the cause.

We didn't get a log. The log was not at $JUJU_HOME/local/log/all-machines.log as it has been in the past. This is the output from the test, which does not reveal much.
    http://162.213.35.54:8080/job/local-upgrade/786/console

I will retest and tail the log to capture something meaningful.

[Curtis Hovey (sinzui)]

unit-mysql-0.log
    2014-02-19 19:20:09 ERROR juju runner.go:211 worker: exited "upgrader": cannot read tools metadata in tools directory: open /var/lib/juju/tools/1.17.3.1-precise-amd64/downloaded-tools.txt: no such file or directory

unit-wordpress-0.log
    2014-02-19 19:20:21 ERROR juju runner.go:211 worker: exited "upgrader": cannot read tools metadata in tools directory: open /var/lib/juju/tools/1.17.3.1-precise-amd64/downloaded-tools.txt: no such file or directory

The machine logs also report errors, but they are about new version, restart, and it appears to recover and set about asking the units to upgrade.

[Curtis Hovey (sinzui)]

I don't see any dir for the 1.17 tools that were uploaded.
$ ls /var/lib/juju/tools/
1.16.3-precise-amd64 1.16.5-precise-amd64 machine-1 unit-jenkins-0