Yeah, live tests take their time :) So that password change is an issue, as it is interactive and we can't workaround that easily (but if you find a way, it would be very welcome!). The same happened with CloudSigma, and we ended up using a template that supported cloud-init and did not request the password change.
You can pass the "jclouds.template" property to set the template that the live tests will use, and you should configure the property with a template that works in the provider's metadata default properties (look at CloudSigma or DigitalOcean). Let's see if there is an image that does not require the password change. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/145#issuecomment-77327875
