Clay B. created CLOUDSTACK-370:
----------------------------------
Summary: SSVM fails to download ISO using HTTP if hostname begins
with FTP
Key: CLOUDSTACK-370
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-370
Project: CloudStack
Issue Type: Bug
Components: ISO
Affects Versions: pre-4.0.0
Reporter: Clay B.
Priority: Minor
I am trying to add the following ISO to my Cloud Stack ISOs:
http://ftp.linux.ncsu.edu/pub/CentOS/5.8/isos/x86_64/CentOS-5.8-x86_64-netinstall.iso
(Note it is using the HTTP protocol but the hostname starts with ftp.)
It works happily from
http://mirror.nexcess.net/CentOS/5.8/isos/x86_64/CentOS-5.8-x86_64-netinstall.iso
I see the following on the UI under my attempted ISO add:
Status Failed to install: unsupported protocol: 'ftp'
I see the following error in my SSVM /var/log/cloud/cloud.log:
java.lang.IllegalStateException: unsupported protocol: 'ftp'
at
org.apache.commons.httpclient.protocol.Protocol.lazyRegisterProtocol(Protocol.java:149)
at
org.apache.commons.httpclient.protocol.Protocol.getProtocol(Protocol.java:117)
at org.apache.commons.httpclient.HttpHost.<init>(HttpHost.java:107)
at
org.apache.commons.httpclient.HttpMethodBase.setURI(HttpMethodBase.java:280)
at
org.apache.commons.httpclient.HttpMethodDirector.processRedirectResponse(HttpMethodDirector.java:616)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:179)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at
com.cloud.storage.template.HttpTemplateDownloader.download(HttpTemplateDownloader.java:225)
at
com.cloud.storage.template.HttpTemplateDownloader.run(HttpTemplateDownloader.java:377)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
--
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
