Hugo Trippaers created CLOUDSTACK-3139:
------------------------------------------
Summary: TemplateServiceImpl.handleTemplateSync does not take the
sec storage.proxy settings into account resulting in download errors
Key: CLOUDSTACK-3139
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3139
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
Reporter: Hugo Trippaers
The following bit of code tries to get the template size from an http or https
connection. If the secondary storage is behind a proxy this fails with the
error below.
_resourceLimitMgr.checkResourceLimit(_accountMgr.getAccount(accountId),
com.cloud.configuration.Resource.ResourceType.secondary_storage,
tmpltInfo.getSize() -
UriUtils.getRemoteSize(tmplt.getUrl()));
2013-06-22 13:17:31,265 ERROR [agent.manager.AgentManagerImpl]
(AgentConnectTaskPool-3:null) Monitor DownloadListener says there is an error
in the connect process for 5 due to null
java.lang.NumberFormatException: null
at java.lang.Long.parseLong(Long.java:404)
at java.lang.Long.parseLong(Long.java:483)
at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:113)
at
org.apache.cloudstack.storage.image.TemplateServiceImpl.handleTemplateSync(TemplateServiceImpl.java:328)
at
com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:307)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:583)
at
com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:1083)
at
com.cloud.agent.manager.AgentManagerImpl.access$1(AgentManagerImpl.java:1075)
at
com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.run(AgentManagerImpl.java:1158)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
--
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
