search

wildfly-extras / sunstone

Simple Java library which helps to control virtual machines in cloud environments
Apache License 2.0
6 stars 17 forks source link

AzureTest intermittent failures #1

Open kwart opened 8 years ago

kwart commented 8 years ago

The AzureTest sometime hangs during node.kill() call (i.e. 2nd suspend of the VM).

We could try if the behavior change depending on deallocating the VM in Azure.

kwart commented 8 years ago

Another one seen on Azure (PR #40):

Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 894.747 sec <<< FAILURE! - in org.wildfly.extras.sunstone.tests.azure.AzureTest
node(org.wildfly.extras.sunstone.tests.azure.AzureTest)  Time elapsed: 893.739 sec  <<< ERROR!
java.util.concurrent.CompletionException: org.jclouds.http.HttpResponseException: command: DELETE https://management.core.windows.net/2586c64b-38b4-4527-a140-012d49dfc02c/services/disks/sst-jcacek-361-sst-jcacek-361-0-201608181341580105 HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [<Error xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><Code>BadRequest</Code><Message>A disk with name sst-jcacek-361-sst-jcacek-361-0-201608181341580105 is currently in use by virtual machine sst-jcacek-361 running within hosted service sst-jcacek-361, deployment sst-jcacek-361.</Message></Error>]
Caused by: org.jclouds.http.HttpResponseException: command: DELETE https://management.core.windows.net/2586c64b-38b4-4527-a140-012d49dfc02c/services/disks/sst-jcacek-361-sst-jcacek-361-0-201608181341580105 HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [<Error xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><Code>BadRequest</Code><Message>A disk with name sst-jcacek-361-sst-jcacek-361-0-201608181341580105 is currently in use by virtual machine sst-jcacek-361 running within hosted service sst-jcacek-361, deployment sst-jcacek-361.</Message></Error>]

@Ladicek do you know why I don't see a full stack trace for this error? Is it due to our logging config? Or maven/surefire?

Ladicek commented 8 years ago

@kwart I think the full exception should be visible in Surefire logs. I don't really know how Surefire decides whether to show the stack trace on normal console output or not -- I'm 100% sure I had to look it up in the Surefire logs on multiple occasions, but I'd also swear that I've seen it in the console several times...