[ https://issues.apache.org/jira/browse/CLOUDSTACK-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Min Chen resolved CLOUDSTACK-3175. ---------------------------------- Resolution: Fixed Based on latest BVT test report on master, this has been fixed. http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/lastCompletedBuild/suite=test_volumes/testReport/ > DetachVolume command fails with Internal Server Error > ----------------------------------------------------- > > Key: CLOUDSTACK-3175 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3175 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.2.0 > Reporter: Prasanna Santhanam > Assignee: Min Chen > Priority: Critical > Fix For: 4.2.0 > > Attachments: 433.tar.bz2 > > > The detach volume command fails with the following exception during resize > and other volume operations. > Jun 24 19:02:19 cloudstack-centos63 local0: 2013-06-25 02:02:19,529 ERROR > [cloud.async.AsyncJobManagerImpl] (Job-Executor-112:job-219) Unexpected > exception while executing > org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd > Jun 24 19:02:19 cloudstack-centos63 > com.cloud.utils.exception.CloudRuntimeException: Failed to detach volume: > TestDiskServ from VM: 6cfa189d-5b8c-45d3-84c6-2849f7a01ddf; Failed dettach > volume: 43411042-0287-48aa-9909-70dcd0bba273, due to The server failed to > handle your request, due to an internal error. The given message may give > details useful for debugging the problem. > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.storage.VolumeManagerImpl.detachVolumeFromVM(VolumeManagerImpl.java:1939) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > Jun 24 19:02:19 cloudstack-centos63 at > org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:133) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > Jun 24 19:02:19 cloudstack-centos63 at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.FutureTask.run(FutureTask.java:166) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > Jun 24 19:02:19 cloudstack-centos63 at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > Jun 24 19:02:19 cloudstack-centos63 at > java.lang.Thread.run(Thread.java:679) > This was seen on master (af91a8ac8de4ce73bafd8caf9b2cc1bd73bdb444) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira