Comment 0 for bug 1257371

juju-core r2116 fails to bootstrap on canonistack and aws. The tests passed yesterday (r2113). We were not able to capture logs for the failed bootstrap. The issue may be in r2116 which introduced synchronous bootstrap.

2013-12-03 15:39:17 INFO juju.provider.openstack provider.go:733 started instance "1a217478-f6f9-44ca-beb6-a87834ffdc7b"
 - 1a217478-f6f9-44ca-beb6-a87834ffdc7b
Waiting for DNS name..............
 - 10.55.32.197
Attempting to connect to 10.55.32.197:22.....
2013-12-03 15:40:01 INFO juju.cloudinit.sshinit configure.go:24 Provisioning machine agent on ubuntu@10.55.32.197
Pseudo-terminal will not be allocated because stdin is not a terminal.
Warning: Permanently added '10.55.32.197' (ECDSA) to the list of known hosts.
Permission denied (publickey).
Stopping instance...
2013-12-03 15:40:02 ERROR juju supercommand.go:282 exit status 255
Command '('juju', 'bootstrap', '-e', 'test-release-canonistack', '--constraints', 'mem=2G', '--show-log')' returned non-zero exit status 1
+ EXIT_STATUS=1

I am attaching the full jenkins logs for canonistack and aws.