As seen at
http://reports.vapour.ws/releases/issue/57d80496749a56567fd47cfc
Juju cannot bootstrap because the session is not authenticated. this error is seen *after* work has started, implying juju had an authenticated session.
ERROR cmd supercommand.go:458 failed to bootstrap model: cannot start bootstrap instance: Can't create instance in any of availability zones, last error: ServerFaultCode: The session is not authenticated.
2016-09-13 03:38:24 ERROR Command '('juju', '--show-log', 'bootstrap', '--constraints', 'mem=2G', 'vsphere-deploy-trusty-amd64', 'vsphere/dc0', '--config', '/tmp/tmpctNFpF.yaml', '--default-model', 'vsphere-deploy-trusty-amd64', '--agent-version', '2.0-rc1', '--bootstrap-series', 'trusty')' returned non-zero exit status 1
I cant manage to reproduce this I believe it might have been caused by the misuse of sessions (excess of open sessions would make new ones behave oddly, like this one)