[jira] [Resolved] (CLOUDSTACK-2668) [Object_STore_Refactor]Upload volume failed with CloudRuntimeException when s3 is being used as storage provider

["Min Chen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Min Chen resolved CLOUDSTACK-2668.
----------------------------------

    Resolution: Fixed

Not reproducible in latest object_store, may have been fixed by Edison.
                
> [Object_STore_Refactor]Upload volume failed with CloudRuntimeException when s3 is being used as storage provider
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2668
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2668
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Latest build from object_store branch: CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>            Reporter: Sanjeev N
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Upload volume failed with CloudRuntimeException when s3 is being used as storage provider
> Steps to Reproduce:
> =================
> 1.Bring up CS in advanced zone with S3 as the secondary storage provider
> 2.Try to upload volume using following API:
> http://10.147.59.119:8096/client/api?command=uploadVolume&format=VHD&name=cent62&url=http://10.147.28.7/templates/CentOS62-64bit/280c2a70-e37f-4863-bff8-d318122fd61b.vhd&zoneid=ab0cac49-0ba0-47b6-acc7-a79803852bc7
> Result:
> =====
> 2013-05-24 11:22:13,752 DEBUG [agent.transport.Request] (DirectAgent-424:null) Seq 1-698155012: Processing:  { Ans: , MgmtId: 7332683579487, via: 1, Ver: v1, Flags: 10, [{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}] }
> 2013-05-24 11:22:25,219 DEBUG [cloud.async.AsyncJobManagerImpl] (ApiServer-1:null) submit async job-24, details: AsyncJobVO {id:24, userId: 1, accountId: 1, sessionKey: null, instanceType: None, instanceId: null, cmd: org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd, cmdOriginator: null, cmdInfo: {"ctxUserId":"1","zoneid":"ab0cac49-0ba0-47b6-acc7-a79803852bc7","name":"cent62","httpmethod":"GET","ctxAccountId":"1","format":"VHD","ctxStartEventId":"87","url":"http://10.147.28.7/templates/CentOS62-64bit/280c2a70-e37f-4863-bff8-d318122fd61b.vhd"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 7332683579487, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-05-24 11:22:25,227 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-24) Executing org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd for job-24
> 2013-05-24 11:22:25,439 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-24) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to update state:com.cloud.utils.exception.CloudRuntimeException: Failed to transit volume: 9, due to: com.cloud.utils.fsm.NoTransitionException: Unable to transition to a new state from UploadOp via null
>         at org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:228)
>         at org.apache.cloudstack.storage.volume.VolumeServiceImpl.registerVolume(VolumeServiceImpl.java:824)
>         at com.cloud.storage.VolumeManagerImpl.uploadVolume(VolumeManagerImpl.java:397)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at com.cloud.storage.VolumeManagerImpl.uploadVolume(VolumeManagerImpl.java:183)
>         at org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd.execute(UploadVolumeCmd.java:121)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
>         at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
>         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:1146)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-05-24 11:22:25,441 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-24) Complete async job-24, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to update state:com.cloud.utils.exception.CloudRuntimeException: Failed to transit volume: 9, due to: com.cloud.utils.fsm.NoTransitionException: Unable to transition to a new state from UploadOp via null

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