You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/07/29 08:45:51 UTC

[jira] [Assigned] (CLOUDSTACK-992) Template creations dies after 2h for no reason

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

Prasanna Santhanam reassigned CLOUDSTACK-992:
---------------------------------------------

    Assignee:     (was: Prasanna Santhanam)

Not working on this
                
> Template creations dies after 2h for no reason
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-992
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-992
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM, Template
>    Affects Versions: 4.0.0
>         Environment: KVM@CentOS, Fuse-mounted MooseFS as storage
>            Reporter: Martin Zorawski
>             Fix For: 4.2.0
>
>
> Template creation dies after 2h, despite 3h wait time set in global setting ( and sent in log below ).
> Template .qcow2 file is made to the end properly, but there are no template.properties file and database entry. No exception reason is mentioned.
> Since secondary storage uses NFS to mount fuse storage its efficiency is low - it affects all bigger templates
> Smallers can be made without any problem. 
> 2013-01-16 10:00:23,466 DEBUG [agent.transport.Request] (StatsCollector-1:null) Seq 12-1218033812: Received:  { Ans: , MgmtId: 345051234375, via: 12, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
> 2013-01-16 10:33:04,018 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-12:null) submit async job-3812, details: AsyncJobVO {id:3812, userId: 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 251, cmd: com.cloud.api.commands.CreateTemplateCmd, cmdOriginator: null, cmdInfo: {"sessionkey":"EpxODReTap/knYDQUDA6f2uK/Eo\u003d","volumeId":"f2d5134c-3420-4701-9e43-01389d07ca05","ctxUserId":"2","osTypeId":"ead3d52a-6bf9-4347-939f-cb632164c819","isPublic":"true","isfeatured":"true","response":"json","id":"251","displayText":"Pro N","passwordEnabled":"false","name":"Win7","_":"1358332957307","ctxAccountId":"2","ctxStartEventId":"13892"}, cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 345051234375, completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-01-16 10:33:04,199 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-70:job-3812) Executing com.cloud.api.commands.CreateTemplateCmd for job-3812
> 2013-01-16 10:33:04,292 DEBUG [agent.transport.Request] (Job-Executor-70:job-3812) Seq 12-1218033892: Sending  { Cmd , MgmtId: 345051234375, via: 12, Ver: v1, Flags: 100011, [{"CreatePrivateTemplateFromVolumeCommand":{"_vmName":"i-2-36-VM","_volumePath":"eb967824-2881-4222-9bfa-c1f3817d2e08","_userSpecifiedName":"Win7","_uniqueName":"8bd3dc0d-20ff-469f-bc2d-5596e9b5d4cb","_templateId":251,"_accountId":2,"_secondaryStorageUrl":"nfs://junk/export/secondary","primaryStoragePoolNameLabel":"a17316fe-c778-4ef2-847d-00dce1e6d2b0","wait":10800}}] }
> 2013-01-16 12:33:07,115 DEBUG [agent.transport.Request] (Job-Executor-70:job-3812) Seq 12-1218033892: Received:  { Ans: , MgmtId: 345051234375, via: 12, Ver: v1, Flags: 10, { CreatePrivateTemplateAnswer } }
> 2013-01-16 12:33:07,511 ERROR [cloud.api.ApiDispatcher] (Job-Executor-70:job-3812) Exception while executing CreateTemplateCmd:
> 2013-01-16 12:33:07,511 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-70:job-3812) Complete async job-3812, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to create a template
> 2013-01-16 12:33:08,878 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-23:null) Async job-3812 completed

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