This is the live test output: chef: Tests run: 66, Failures: 0, Errors: 0, Skipped: 0 google-compute-engine: Tests run: 179, Failures: 0, Errors: 0, Skipped: 8 packet: Tests run: 53, Failures: 0, Errors: 0, Skipped: 0 azurecompute-arm: Tests run: 242, Failures: 9, Errors: 0, Skipped: 75
Skipped tests in Azure are just the KeyVault ones. I don't have the properties configured so those tests are skipped. Apart from that, there are 9 failures due to SSH authentication issues to some deployed VMs. This will need further investigation, but I don't think we should block the release for this given it is a release requested by some users that don't directly depend on Azure. I've also tested the aws-ec2 provider with the jclouds-examples compute-basics project and no errors were found. On Thu, 9 Aug 2018 at 15:30, Ignasi Barrera <n...@apache.org> wrote: > > This thread is for discussion of the first release candidate for > Apache jclouds 2.1.1. > > Please use this thread for discussion of issues uncovered in the RC, > questions you may have about the RC, etc. > > If you want to help to validate the release, you'll find a set of > scripts and the corresponding instructions here: > https://cwiki.apache.org/confluence/display/JCLOUDS/Validate+a+Release > > You can also go run live tests for your preferred providers and post > the results here, or use the projects in the jclouds-examples repo, > such as the "compute-basics" to rapidly smoke test the providers you > are interested in: > https://github.com/jclouds/jclouds-examples > > > Thank you!
