cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4330) [Automation] [Vmware] Attach volume test cases failed from BVT
Date Thu, 15 Aug 2013 04:48:47 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740674#comment-13740674
] 

Animesh Chaturvedi commented on CLOUDSTACK-4330:
------------------------------------------------

Rayees can you try this manually to validate if this is a script or product issue
                
> [Automation] [Vmware] Attach volume test cases failed from BVT 
> ---------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4330
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4330
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, VMware, Volumes
>    Affects Versions: 4.2.0
>         Environment: VMware
> 4.2
>            Reporter: Rayees Namathponnan
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: management-server.log.2013-08-11.gz
>
>
> Below test cases failed from vmware suite with Aug 11th build, we dont have latest build
to test these issue,  vmware automation blocked due to CLOUDSTACK-4288
> integration.smoke.test_volumes.TestVolumes.test_03_download_attached_volume
> integration.smoke.test_volumes.TestVolumes.test_04_delete_attached_volume
> integration.smoke.test_volumes.TestVolumes.test_05_detach_volume
> integration.smoke.test_volumes.TestVolumes.test_06_download_detached_volume
> integration.smoke.test_volumes.TestVolumes.test_02_attach_volume
> integration.smoke.test_volumes.TestVolumes.test_07_resize_fail
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 
> Test cases failed while attaching volume, observed below error in MS log; attached completed
log
> 2013-08-11 12:36:02,678 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-215:null)
Seq 2-306512410: Response Received: 
> 2013-08-11 12:36:02,678 DEBUG [agent.transport.Request] (DirectAgent-215:null) Seq 2-306512410:
Processing:  { Ans: , MgmtId: 90928106758026, via: 2, Ver: v1, Flags: 10, [{"org.apache.cloudstack.storage.command.AttachAnswer":{"result":false,"details":"AttachVolumeCommand
failed due to Exception: java.lang.RuntimeException\nMessage: Unable to access file [4faf04c26dd83025b43f65d32cc49d02]
i-25-46-TestVM/1849c225bdb84962a4902adfe66192b0-flat.vmdk\n","wait":0}}] }
> 2013-08-11 12:36:02,679 DEBUG [agent.transport.Request] (Job-Executor-154:job-144 = [
2310830f-8a06-44d4-8ef4-c48b05e20fbe ]) Seq 2-306512410: Received:  { Ans: , MgmtId: 90928106758026,
via: 2, Ver: v1, Flags: 10, { AttachAnswer } }
> 2013-08-11 12:36:02,683 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-154:job-144
= [ 2310830f-8a06-44d4-8ef4-c48b05e20fbe ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume: TestDiskServ
to VM: df231d16-32f0-4781-87aa-74f65f593d57; AttachVolumeCommand failed due to Exception:
java.lang.RuntimeException
> Message: Unable to access file [4faf04c26dd83025b43f65d32cc49d02] i-25-46-TestVM/1849c225bdb84962a4902adfe66192b0-flat.vmdk
> 	at com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1688)
> 	at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1895)
> 	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> 	at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> 	at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> 	at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> 	at java.lang.Thread.run(Thread.java:722)
> 2013-08-11 12:36:02,685 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-154:job-144
= [ 2310830f-8a06-44d4-8ef4-c48b05e20fbe ]) Complete async job-144 = [ 2310830f-8a06-44d4-8ef4-c48b05e20fbe
], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to attach volume:
TestDiskServ to VM: df231d16-32f0-4781-87aa-74f65f593d57; AttachVolumeCommand failed due to
Exception: java.lang.RuntimeException
> Message: Unable to access file [4faf04c26dd83025b43f65d32cc49d02] i-25-46-TestVM/1849c225bdb84962a4902adfe66192b0-flat.vmdk
> 2013-08-11 12:36:02,730 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-12:null)
submit async job-145 = [ 2ca9dec4-0427-4d4b-9e5e-969bdd85603b ], details: AsyncJobVO {id:145,
userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine, instanceId: 29, cmd:
org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, cmdOriginator: null, cmdInfo: {"response":"json","id":"7964adc6-242b-4873-bee3-b3d8ff2de7da","cmdEventType":"VM.DESTROY","ctxUserId":"2","httpmethod":"GET","ctxAccountId":"2","ctxStartEventId":"653","apiKey":"duOaDswm26xm4Ag3h5OWpEvgMzus4V-YxEMK3x463iQWgRLO650H8ANrky7rYVlrBVW-gBbz61uOdc_KVYHoJg","signature":"fpkDcTnwCWKjVSq9HhMCdNotlpQ\u003d"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode:
0, result: null, initMsid: 90928106758026, completeMsid: null, lastUpdated: null, lastPolled:
null, created: null}
> 2013-08-11 12:36:02,732 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) ===END===
 10.223.240.195 -- GET  signature=fpkDcTnwCWKjVSq9HhMCdNotlpQ%3D&apiKey=duOaDswm26xm4Ag3h5OWpEvgMzus4V-YxEMK3x463iQWgRLO650H8ANrky7rYVlrBVW-gBbz61uOdc_KVYHoJg&command=destroyVirtualMachine&id=7964adc6-242b-4873-bee3-b3d8ff2de7da&response=json
> 2013-08-11 12:36:02,733 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-155:job-145
= [ 2ca9dec4-0427-4d4b-9e5e-969bdd85603b ]) Executing org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
for job-145 = [ 2ca9dec4-0427-4d4b-9e5e-969bdd85603b ]
> 2013-08-11 12:36:02,736 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null) ===START===
 10.223.240.195 -- GET  signature=%2FyVG2mKzHWke9apZuSAntvlEXP8%3D&apiKey=duOaDswm26xm4Ag3h5OWpEvgMzus4V-YxEMK3x463iQWgRLO650H8ANrky7rYVlrBVW-gBbz61uOdc_KVYHoJg&command=queryAsyncJobResult&response=json&jobid=2ca9dec4-0427-4d4b-9e5e-969bdd85603b
> 2013-08-11 12:36:02,759 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null) ===END===
 10.223.240.195 -- GET  signature=%2FyVG2mKzHWke9apZuSAntvlEXP8%3D&apiKey=duOaDswm26xm4Ag3h5OWpEvgMzus4V-YxEMK3x463iQWgRLO650H8ANrky7rYVlrBVW-gBbz61uOdc_KVYHoJg&command=queryAsyncJobResult&response=json&jobid=2ca9dec4-0427-4d4b-9e5e-969bdd85603b
> 2013-08-11 12:36:02,769 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-155:job-145
= [ 2ca9dec4-0427-4d4b-9e5e-969bdd85603b ]) Destroying vm VM[User|7964adc6-242b-4873-bee3-b3d8ff2de7da]
> 2013-08-11 12:36:02,774 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-155:job-145
= [ 2ca9dec4-0427-4d4b-9e5e-969bdd85603b ]) VM state transitted from :Running to Stopping
with event: StopRequestedvm's original host id: 2 new host id: 2 host id before state transition:
2
> 2013-08-11 12:36:02,777 DEBUG [agent.transport.Request] (Job-Executor-155:job-145 = [
2ca9dec4-0427-4d4b-9e5e-969bdd85603b ]) Seq 2-306512411: Sending  { Cmd , MgmtId: 90928106758026,
via: 2, Ver: v1, Flags: 100011, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-19-29-TestVM","wait":0}}]
}
> 2013-08-11 12:36:02,777 DEBUG [agent.transport.Request] (Job-Executor-155:job-145 = [
2ca9dec4-0427-4d4b-9e5e-969bdd85603b ]) Seq 2-306512411: Executing:  { Cmd , MgmtId: 90928106758026,
via: 2, Ver: v1, Flags: 100011, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-19-29-TestVM","wait":0}}]
}
> 2013-08-11 12:36:02,777 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-359:null)
Seq 2-306512411: Executing request
> 2013-08-11 12:36:02,777 INFO  [vmware.resource.VmwareResource] (DirectAgent-359:10.223.250.131)
Executing resource StopCommand: {"isProxy":false,"executeInSequence":false,"vmName":"i-19-29-TestVM","wait":0}
> 2013-08-11 12:36:02,777 DEBUG [vmware.mo.HostMO] (DirectAgent-359:10.223.250.131) find
VM i-19-29-TestVM on host
> 2013-08-11 12:36:02,777 INFO  [vmware.mo.HostMO] (DirectAgent-359:10.223.250.131) VM
i-19-29-TestVM not found in host cache

--
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

Mime
View raw message