> + List<SharedStorageAccess> access =
> sharedStorageApi().getAccessCredentials();
> +
> + assertNotNull(access);
> + assertTrue(access.size() > 0);
> + }
> +
> + public void testChangePassword() throws InterruptedException {
> + List<SharedStorageAccess> response =
> sharedStorageApi().changePassword(SharedStorageAccess.UpdateSharedStorageAccess.create("Test123!"));
> +
> + assertNotNull(response);
> + }
> +
> + @AfterClass(alwaysRun = true)
> + public void teardownTest() throws InterruptedException {
> + sharedStorageApi().delete(currentSharedStorage.id());
> + assertNodeAvailable(currentServer);
Does it make sense to try to delete the server even if the shared storage
delete operation failed? We should try to avoid leaking resources.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/304/files/b4ecd2bdfe26ff68d6dd6c9e03a4de2e3eba3fe2#r72953981
