Rayees Namathponnan created CLOUDSTACK-4273:
-----------------------------------------------

             Summary: [Automation] Volume test cases fails from BVT, test cases 
failed during attachment 
                 Key: CLOUDSTACK-4273
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4273
             Project: CloudStack
          Issue Type: Test
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: API, Automation
    Affects Versions: 4.2.0
         Environment: Automation 
            Reporter: Rayees Namathponnan
            Priority: Blocker
             Fix For: 4.2.0


Below two test cases failed with last run 

integration.smoke.test_volumes.TestVolumes.test_07_resize_fail
integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 


Test cases  performing below steps

1 ) Create volume 
2 ) Attach volume to VM
3) Extract volume 
4) Detach volume and attach again . 



Attachment failed, observed below error in log 

2013-07-16 16:22:04,331 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-24:null) submit async job-146 = [ 
5b11343d-fa1c-4827-b952-02afa4452001 ], details: AsyncJobVO {id:146, userId:
2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 35, cmd: 
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd, cmdOriginator: 
null, cmdInfo: {"response":"json",
"id":"86ac4a51-70c4-4df1-8c80-95078da84d24","virtualmachineid":"c8162e00-029f-499a-abd6-0340609e5969","cmdEventType":"VOLUME.ATTACH","ctxUserId":"2","httpmethod":"GET","ctxAccountId":"2","ct
xStartEventId":"611","apiKey":"kOrywOTuIhHSb9q1EjAMHOeAiCx9gnQlZjPgWfLlcMc701gGcNPaZcK5X_UWCplOnKH4Oxrl_ZVd6JOO0lBTFQ","signature":"sTwWb+gAsY+dE3N/m4DSOrdtlcc\u003d"},
 cmdVersion: 0, callba
ckType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode: 0, 
result: null, initMsid: 29066118877352, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2013-07-16 16:22:04,331 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-3:job-146 = [ 5b11343d-fa1c-4827-b952-02afa4452001 ]) Executing 
org.apache.cloudstack.api.command.user.volume.At
tachVolumeCmd for job-146 = [ 5b11343d-fa1c-4827-b952-02afa4452001 ]
2013-07-16 16:22:04,338 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) 
===END===  10.223.240.194 -- GET  
apiKey=kOrywOTuIhHSb9q1EjAMHOeAiCx9gnQlZjPgWfLlcMc701gGcNPaZcK5X_UWCplOnKH4Oxrl
_ZVd6JOO0lBTFQ&virtualmachineid=c8162e00-029f-499a-abd6-0340609e5969&id=86ac4a51-70c4-4df1-8c80-95078da84d24&command=attachVolume&signature=sTwWb%2BgAsY%2BdE3N%2Fm4DSOrdtlcc%3D&response=json
2013-07-16 16:22:04,342 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null) 
===START===  10.223.240.194 -- GET  
signature=%2ByObUNeazGs40aCfSYrQZPlUwjY%3D&apiKey=kOrywOTuIhHSb9q1EjAMHOeAiCx
9gnQlZjPgWfLlcMc701gGcNPaZcK5X_UWCplOnKH4Oxrl_ZVd6JOO0lBTFQ&command=queryAsyncJobResult&response=json&jobid=5b11343d-fa1c-4827-b952-02afa4452001
2013-07-16 16:22:04,440 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null) 
===END===  10.223.240.194 -- GET  
signature=%2ByObUNeazGs40aCfSYrQZPlUwjY%3D&apiKey=kOrywOTuIhHSb9q1EjAMHOeAiCx9g
nQlZjPgWfLlcMc701gGcNPaZcK5X_UWCplOnKH4Oxrl_ZVd6JOO0lBTFQ&command=queryAsyncJobResult&response=json&jobid=5b11343d-fa1c-4827-b952-02afa4452001
2013-07-16 16:22:04,454 ERROR [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-3:job-146 = [ 5b11343d-fa1c-4827-b952-02afa4452001 ]) Unexpected 
exception while executing org.apache.cloudstack
.api.command.user.volume.AttachVolumeCmd
com.cloud.exception.InvalidParameterValueException: Volume is not uploaded yet. 
Please try this operation once the volume is uploaded
        at 
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1844)
        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:679)
2013-07-16 16:22:04,456 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-3:job-146 = [ 5b11343d-fa1c-4827-b952-02afa4452001 ]) Complete 
async job-146 = [ 5b11343d-fa1c-4827-b952-02afa4452001 ], jobStatus: 2, 
resultCode: 530, result: Error Code: 530 Error text: Volume is not uploaded 
yet. Please try this operation once the volume is uploaded
2013-07-16 16:22:05,136 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-20:null) Ping from 1
2013-07-16 16:22:06,537 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null) 
===START===  10.223.240.194 -- GET  
signature=gGMyHy40b1SizZx6eAbVrAY5qAY%3D&apiKey=kOrywOTuIhHSb9q1EjAMHOeAiCx9gnQlZjPgWfLlcMc701gGcNPaZcK5X_UWCplOnKH4Oxrl_ZVd6JOO0lBTFQ&command=queryAsyncJobResult&response=json&jobid=26293b74-c64b-4d89-92a5-06a626d023b0
2013-07-16 16:22:06,563 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null) 
===END===  10.223.240.194 -- GET  
signature=gGMyHy40b1SizZx6eAbVrAY5qAY%3D&apiKey=kOrywOTuIhHSb9q1EjAMHOeAiCx9gnQlZjPgWfLlcMc701gGcNPaZcK5X_UWCplOnKH4Oxrl_ZVd6JOO0lBTFQ&command=queryAsyncJobResult&response=json&jobid=26293b74-c64b-4d89-92a5-06a626d023b0
2013-07-16 16:22:06,927 DEBUG [agent.manager.AgentManagerImpl] 
(AgentManager-Handler-10:null) SeqA 6-282: Processing Seq 6-282:  { Cmd , 
MgmtId: -1, via: 6, Ver: v1, Flags: 11, 
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
  \"connections\": []\n}","wait":0}}] }


 


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

Reply via email to