You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/05/09 17:01:23 UTC
[jira] [Closed] (CLOUDSTACK-2054) [Automation]Failed to upload
volume with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rayees Namathponnan closed CLOUDSTACK-2054.
-------------------------------------------
Resolution: Cannot Reproduce
Tested with latest build, not found this issue.
> [Automation]Failed to upload volume with NPE
> --------------------------------------------
>
> Key: CLOUDSTACK-2054
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2054
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Volumes
> Affects Versions: 4.2.0
> Environment: KVM and VMware
> Reporter: Rayees Namathponnan
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2054.rar
>
>
> Found this issue while executing regression test case "test_upload_volumes.py"
> Step 1 : Create master build, install and configure advanced zone
> Step 2 : upload volume ".vhd" file , size 1 GB
> Actual result
> Upload failed with NPE
> eryAsyncJobResult&jobId=960459e9-a299-4552-a56c-d11522271c4d&response=json&sessionkey=vp9T6C4z5OzLwUgMljRFFe2bUo0%3D&_=1366147860238
> 2013-04-16 17:34:00,975 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-2285) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd
> java.lang.NumberFormatException: null
> at java.lang.Long.parseLong(Long.java:401)
> at java.lang.Long.parseLong(Long.java:478)
> at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:95)
> at com.cloud.storage.VolumeManagerImpl.validateVolume(VolumeManagerImpl.java:478)
> at com.cloud.storage.VolumeManagerImpl.uploadVolume(VolumeManagerImpl.java:377)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at com.cloud.storage.VolumeManagerImpl.uploadVolume(VolumeManagerImpl.java:175)
> at org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd.execute(UploadVolumeCmd.java:121)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164)
> 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:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-16 17:34:00,976 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-2285) Complete async job-2285, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null
> 2013-04-16 17:34:01,620 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2 is ready to launch secondary storage VM
> 2013-04-16 17:34:02,028 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 2 is ready to launch console proxy
--
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