upgrade-juju doesn't for all providers

[Curtis Hovey]

CI fails the juju upgrade tests for all providers (aws, hp, azure, joyent, and local) in trunk. In all cases the test gives up. Even after changing the tests to wait 30 minutes and continue to try when there is to state-server, the tests fail.

trunk has not has a successful revision since lp:juju-core r2587. Juju-upgrade completed in less 2 minutes for all providers. The tests had a timeout set for 10 minutes. (other than azure, the tests themselves only take between 5 and 10 minutes). Logs cannot be collected because the state-server is down, blocking the user of juju scp.

[Nate Finch (natefinch)]

I have a fix for this here: https://codereview.appspot.com/86930046

[John A Meinel (jameinel)]

Nate: for future reference, you can "Link a related branch" on the right hand column, which will show the requested merge, and indicate when it has landed, etc.

Also, if you "bzr commit --fixes lp:1306358" when committing your changes, then when you "bzr push" to Launchpad it will automatically link the branch, and when the landing bot merges your code, it will automatically change the status to Fix Committed.