Hi @nacx !
So 11 of the live tests were green; the failed tests were related to the ssh flow like:
<pre>
org.jclouds.ssh.SshException: (root:pw[ca4cb85a391831b122e3277b88393d3f]@46.16.73.251:22)
(root:pw[ca4cb85a391831b122e3277b88393d3f]@46.16.73.251:22) error acquiring ExecResponse(command=[rm
/tmp/init-configure-jetty]) (out of retries - max 5): Read timed out
</pre>
I tried to ssh to the said nodes, and it turns out that this was due to the operating system
requesting a password change after logging in; thus, hanging for so long waiting for an input.
It's a really weird behavior IMO, since I thought this was only applicable if I let the API
generate it's own password. (I emailed PB tech support regards this.)
Assuming this was by design, my next step would be is to connect via SSH right away (to complete
the prerequisites first) before returning the `NodeAndInitialCredentials`. I'm not sure if
there are _hooks_ for something like this, but WDYT? Suggestions?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/145#issuecomment-77312703