I've just run the live tests one more time and now one test is failing always at the same point:
The `testAScriptExecutionAfterBootWithBasicTemplate ` is now failing [here](https://github.com/jclouds/jclouds/blob/master/compute/src/test/java/org/jclouds/compute/internal/BaseComputeServiceLiveTest.java#L309) (the method is disabled as a test but it is called internally). To be more precise, the failure happens here: https://github.com/jclouds/jclouds/blob/master/compute/src/main/java/org/jclouds/compute/callables/SudoAwareInitManager.java#L78 There have not been changes in the code of the provider, and it only fails at that point, after modifying the node credentials and trying to cancel the task. I'm not sure where the issue can be, but the live tests perform many other node access, generate SSH keys, etc, so I'm pretty confident the bouncycastle dependency shouldn't be a problem (but on the other hand, the code in the provider hasn't changed). If you are ok with this, I think it is safe to merge this and the DigitalOcean pull requests (all live tests except that concrete bit are passing and the runscript stuff, which uses the sshj driver, is tested in many ways), and investigate the issue later, as it may take time to isolate. Do you prefer to merge or prefer to wait? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/274#issuecomment-34116447
