Hey User list,
We're seeing problems since upgrading to 2.0.0-SNAPSHOT from
1.8.2-SNAPSHOT. We're using jclouds-labs-google and when trying to
provision nodes, they block forever, despite the node now running:
2014-11-11 20:20:48,988 DEBUG [pool-3-thread-1] [] jclouds.compute
[SLF4JLogger.java:56] << RUNNING node(us-central1-a/test-cluster-6-626)
2014-11-11 20:20:49,001 DEBUG [pool-3-thread-3] [] jclouds.compute
[SLF4JLogger.java:56] >> blocking on sockets [107.178.210.31:22,
10.27.249.104:22] for 600000 MILLISECONDS
2014-11-11 20:20:52,044 DEBUG [pool-3-thread-2] [] jclouds.compute
[SLF4JLogger.java:56] << RUNNING node(us-central1-a/test-cluster-6-bec)
2014-11-11 20:20:52,045 DEBUG [pool-3-thread-8] [] jclouds.compute
[SLF4JLogger.java:56] >> blocking on sockets [146.148.92.89:22,
10.31.244.213:22] for 600000 MILLISECONDS
We haven't changed how we built the template:
builder.imageId(request.image)
.hardwareId(s"${request.zone}/${request.machineType}")
.locationId(request.zone)
.options(options.overrideLoginPrivateKey(Main.conf.privateKeyString))
.options(options.overrideLoginUser(request.sshUserName))
.options(options.authorizePublicKey(Main.conf.publicKeyString))
.build()
The serial output from the instance launched using 2.0.0-SNAPSHOT is here,
it looks like it can't find a boot disk:
https://gist.github.com/ssk2/7bfd47a1ee8965e51bdd
Serial output when the instance launches successfully using 1.8.2-SNAPSHOT
is here: https://gist.github.com/ssk2/19ae56c9f0d5f67cc5a5 using the same
image (backports-debian-7-wheezy-v20141108).
Any suggestions or ideas will be gratefully received :)
Sunil
