incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saksham Srivastava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-91) no error message when we upload volume whose size is greater than storage.max.volume.upload.size value
Date Mon, 01 Oct 2012 15:27:07 GMT

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

Saksham Srivastava commented on CLOUDSTACK-91:
----------------------------------------------

There are separate thread for the job that actually uploads the volume.However listVolumes
shows the correct state of the volume. 
The same state can be seen in the UI when clicking on the particular volume.
listVolume API also returns the upload status of the volume, but the same is not shown on
the UI. So adding a new field (status) in the UI that correctly shows the upload status of
the volume or error string in case of upload error.
                
> no error message when we upload  volume whose size is greater than storage.max.volume.upload.size
value
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-91
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-91
>             Project: CloudStack
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: pre-4.0.0
>         Environment: Git Revision: 03df2fa9dd45c938f72cd1866044b09d1b0cc978
> Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
>            Reporter: shweta agarwal
>            Assignee: Saksham Srivastava
>             Fix For: pre-4.0.0
>
>
> set global config storage.max.volume.upload.size =1
> Restart management server 
> Upload a volume whose size>1GB
> Actual Result:
> Volume goes into uploaderror state without giving error/ reason message 
> Expected Result:
> A message to user/admin  should be displayed stating reason for failure
> Additional information :
> Notice management server Logs shows following entries :
> 2012-09-13 16:17:14,170 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-17:null)
submit async job-44, details: AsyncJobVO {id:44, userId: 2, accountId: 2, sessionKey: null,
instanceType: None, instanceId: null, cmd: com.cloud.api.commands.UploadVolumeCmd, cmdOriginator:
null, cmdInfo: {"response":"json","sessionkey":"D8lyN/UREAYgQ3VEbVwqaEnVauE\u003d","ctxUserId":"2","name":"http://10.147.28.6/templates/centos5.5hvm.vhd.gz","_":"1347533373880","ctxAccountId":"2","format":"VHD","ctxStartEventId":"192","url":"http://10.147.28.6/templates/centos5.5hvm.vhd.gz","zoneId":"3df3d65a-fd70-4a52-942c-b29c3acf1dba"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode:
0, result: null, initMsid: 345052566032, completeMsid: null, lastUpdated: null, lastPolled:
null, created: null}
> 2012-09-13 16:17:14,176 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-1:job-44)
Executing com.cloud.api.commands.UploadVolumeCmd for job-44
> 2012-09-13 16:17:14,240 DEBUG [agent.transport.Request] (Job-Executor-1:job-44) Seq 3-845807624:
Sending  { Cmd , MgmtId: 345052566032, via: 3, Ver: v1, Flags: 100011, [{"storage.DownloadCommand":{"hvm":false,"maxDownloadSizeInBytes":1073741824,"id":16,"resourceType":"VOLUME","url":"http://10.147.28.6/templates/centos5.5hvm.vhd.gz","format":"VHD","accountId":2,"name":"http://10.147.28.6/templates/centos5.5hvm.vhd.gz","secUrl":"nfs://10.147.28.7/export/home/sadhu/xen-sec","wait":0}}]
}
> 2012-09-13 16:17:14,251 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-1:job-44)
Complete async job-44, jobStatus: 1, resultCode: 0, result: com.cloud.api.response.VolumeResponse@6a3bf5e8
> 2012-09-13 16:17:14,280 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-1:job-44)
Done executing com.cloud.api.commands.UploadVolumeCmd for job-44
> 2012-09-13 16:17:14,677 DEBUG [cloud.server.StatsCollector] (StatsCollector-2:null) HostStatsCollector
is running...
> 2012-09-13 16:17:14,686 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-6:null)
Seq 1-1440743435: Executing request
> 2012-09-13 16:17:14,799 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) VmStatsCollector
is running...
> 2012-09-13 16:17:14,814 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-3:null)
Seq 1-1440743436: Executing request
> 2012-09-13 16:17:14,951 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-6:null)
Seq 1-1440743435: Response Received:
> 2012-09-13 16:17:14,952 DEBUG [agent.transport.Request] (StatsCollector-2:null) Seq 1-1440743435:
Received:  { Ans: , MgmtId: 345052566032, via: 1, Ver: v1, Flags: 10, { GetHostStatsAnswer
} }
> 2012-09-13 16:17:15,116 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-3:null)
Vm cpu utilization 0.135
> 2012-09-13 16:17:15,116 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-3:null)
Vm cpu utilization 0.13999999999999999
> 2012-09-13 16:17:15,116 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-3:null)
Vm cpu utilization 0.135
> 2012-09-13 16:17:15,116 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-3:null)
Vm cpu utilization 0.12499999999999999
> 2012-09-13 16:17:15,116 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-3:null)
Seq 1-1440743436: Response Received:
> 2012-09-13 16:17:15,117 DEBUG [agent.transport.Request] (StatsCollector-1:null) Seq 1-1440743436:
Received:  { Ans: , MgmtId: 345052566032, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer }
}
> 2012-09-13 16:17:15,129 DEBUG [cloud.server.StatsCollector] (StatsCollector-3:null) StorageCollector
is running...
> 2012-09-13 16:17:15,185 DEBUG [agent.transport.Request] (StatsCollector-3:null) Seq 3-845807625:
Received:  { Ans: , MgmtId: 345052566032, via: 3, Ver: v1, Flags: 10, { GetStorageStatsAnswer
} }
> 2012-09-13 16:17:15,192 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-7:null)
Seq 1-1440743437: Executing request
> 2012-09-13 16:17:15,810 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-7:null)
Seq 1-1440743437: Response Received:
> 2012-09-13 16:17:15,810 DEBUG [agent.transport.Request] (StatsCollector-3:null) Seq 1-1440743437:
Received:  { Ans: , MgmtId: 345052566032, via: 1, Ver: v1, Flags: 10, { GetStorageStatsAnswer
} }
> 2012-09-13 16:17:17,278 DEBUG [agent.transport.Request] (AgentManager-Handler-6:null)
Seq 3-845807624: Processing:  { Ans: , MgmtId: 345052566032, via: 3, Ver: v1, Flags: 10, [{"storage.DownloadAnswer":{"jobId":"fb652cd6-2cd0-479a-a423-645f5783abf6","downloadPct":0,"errorString":"Download
file size is too large","downloadStatus":"DOWNLOAD_ERROR","downloadPath":"/mnt/SecStorage/14ff52ce-7cce-3300-bfd3-38d6e7244e46/volumes/16/dnld6190746463725337402tmp_","templateSize":0,"templatePhySicalSize":0,"result":false,"details":"Download
file size is too large","wait":0}}] }
> 2012-09-13 16:17:19,251 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-18:null)
Async job-44 completed
> This clearly shows MS log has information of size exceeding the allowable limits.

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