cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Chen (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3791) [DevCloud] Download Template Fails with NPE
Date Mon, 29 Jul 2013 23:31:49 GMT


Min Chen commented on CLOUDSTACK-3791:

Thanks Saksham for confirming. John, for my devcloud experience, I cannot register template
by using a public internet URL as you mentioned in the bug:,
since devcloud does not open network access to internet, so could not reproduce your issue.
Prasanna/John, Please provide your MS log and db dump on your reproducible environment. 
> [DevCloud] Download Template Fails with NPE
> -------------------------------------------
>                 Key: CLOUDSTACK-3791
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.0
>         Environment: devcloud
>            Reporter: John Burwell
>            Priority: Blocker
> When registering a template, the download fails with the following NPE from the SSVM:
> 2013-07-24 17:26:31,364 DEBUG [agent.transport.Request] (AgentManager-Handler-1:null)
Seq 2-1900150803: Processing:  { Ans: , MgmtId: 1, via: 2, Ver: v1, Flags: 10, [{"":{"result":false,"details":"
GetRootDir for null failed due to java.lang.NullPointerException\n\tat\n\tat\n\tat\n\tat\n\tat$AgentRequestHandler.doTask(\n\tat\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(\n\tat
> Secondary storage is configured as NFS on devcloud (nfs://
 The following is the information for the template being registered:
>     Name: CentOS 5.x
>     Description: CentOS 5.x
>     URL:
>     Zone: All Zones
>     Hypervisor: XenServer
>     Format: VHD
>     Extractable: false
>     Password Enabled: false
>     Dynamically Scalable: false
>     Public: true
>     Featured: false

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:

View raw message