1.24.6 fails to bootstrap with "ERROR juju.cmd supercommand.go:430 upgrade in progress - Juju functionality is limited"

[Mike McCracken]

juju 1.24.6 , trusty 14.04.3:

attempting to bootstrap onto a VM enlisted in maas, bootstrap fails repeatably.
the last line in --debug output is here:
ERROR juju.cmd supercommand.go:430 upgrade in progress - Juju functionality is limited

Here's the full contents of juju --debug bootstrap:

http://paste.ubuntu.com/13117526/

[Cheryl Jennings (cherylj)]

When you bootstrap, the agents will update to the latest version of whatever release you're on. In this case, you're bootstrapping with 1.24.6, and 1.24.7 is available. The bootstrap command will wait for 60 seconds for the upgrade to finish before giving up and returning an error. (Granted, it could use some additional information, rather than just returning the upgrade in progress error) It could be that the upgrade was just taking too long, or had failed out and we didn't see it as the error was on the bootstrap node.

You can pin the agent version, an prevent the upgrade by using agent-version: 1.24.6 in your environments.yaml.

Could you try that and see if your bootstrap succeeds? If it does, we could then investigate why the upgrade was not completing within the timeout.

[Mike McCracken (mikemc)]

Yep, pinning the agent version to 1.24.6 worked.

[Cheryl Jennings (cherylj)]

Did you want to try the upgrade to 1.24.7 and see why it took so long (or possibly failed?)

[Cheryl Jennings (cherylj)]

If nothing else, I'd like to better annotate that error you got back from bootstrap. We should be explicit that we timed out waiting for the upgrade to complete.

[Cheryl Jennings (cherylj)]

mikemc was able to do a manual upgrade from 1.24.6 -> 1.24.7 once the environment bootstrapped. I gave him a binary with a longer timeout waiting for the upgrade to complete to check if the issue was just the timeout being too short.