I have ran the live tests and I get some test failures. ``` Results :
Failed tests: ElasticHostsMiamiApiLiveTest>ElasticStackApiLiveTest.testGetDrive:140 » HttpResponse ElasticHostsMiamiApiLiveTest>ElasticStackApiLiveTest.testListDrives:114 » HttpResponse ElasticHostsMiamiApiLiveTest>ElasticStackApiLiveTest.testListStandardDrives:120 » HttpResponse ElasticHostsMiamiTemplateBuilderLiveTest.testDefaultTemplateBuilder:43 expected [true] but found [false] ElasticHostsMiamiComputeServiceLiveTest>BaseComputeServiceLiveTest.testCreateAndRunAService:708->BaseComputeServiceLiveTest.createAndRunAServiceInGroup:746->BaseComputeServiceLiveTest .exec:757->BaseComputeServiceLiveTest.exec:761 » IllegalArgument ElasticHostsMiamiApiLiveTest>ElasticStackApiLiveTest.testCreateAndStartServer:199->ElasticStackApiLiveTest.prepareDrive:360 » HttpResponse ElasticHostsMiamiComputeServiceLiveTest>BaseComputeServiceLiveTest.testAScriptExecutionAfterBootWithBasicTemplate:262->BaseComputeServiceLiveTest.weCanCancelTasks:294 » IllegalArgument ElasticHostsMiamiComputeServiceLiveTest>BaseComputeServiceLiveTest.testCreateTwoNodesWithRunScript:349->BaseComputeServiceLiveTest.checkNodes:510->BaseComputeServiceLiveTest.sshPing:880->BaseComputeServiceLiveTest.doCheckJavaIsInstalledViaSsh:893 » IllegalArgument Tests run: 50, Failures: 8, Errors: 0, Skipped: 15 ``` However, I also get failures when running against a current elastichosts zone, eg lon-b. So I may be configuring the tests incorrectly. I am simply supping the `test.elastichosts-mmi-a.identity` and `test.elastichosts-mmi-a.credential` variables, and just using the defaults for the others. If I am doing it wrong if I could get a valid set of settings (minus identity and credential) for lon-b I could try again on the new providers. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/750#issuecomment-105890198
