Comment 6 for bug 1509097

Looks like it boils down to this:

2015-10-22 21:51:08 INFO juju.worker.upgrader upgrader.go:147 desired tool version: 1.24.7
...
2015-10-22 21:51:08 DEBUG juju.environs.tools urls.go:108 trying datasource "keystone catalog"
...
2015-10-22 21:59:37 ERROR juju.worker runner.go:223 exited "upgrader": no tools available

Did the 1.24.7 tools get put in the openstack deployment's catalog before the upgrade was triggered? Not sure exactly how this is managed in these deployments, but either the machines need to be able to get out to streams.canonical.com or the internal mirroring need to be up to date.

The wrapping script reporting this on bootstrap is confusing, looks like in fact the bootstrap to old version succeeded, but presumably bootstrap to 1.24.7 would have failed with no tools found.