incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimitri Desmidt (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-524) http proxy used by ssvm (secstorage.proxy) NOT working
Date Tue, 20 Nov 2012 14:54:58 GMT
Dimitri Desmidt created CLOUDSTACK-524:

             Summary: http proxy used by ssvm (secstorage.proxy) NOT working
                 Key: CLOUDSTACK-524
             Project: CloudStack
          Issue Type: Bug
          Components: Install and Setup
    Affects Versions: 4.0.0
         Environment: Ubuntu 12.04 - package installation
            Reporter: Dimitri Desmidt

In my lab, the SSVM has access to Internet ONLY via a Proxy.
I configured for that the Global Setting secstorage.proxy with the value ""
(without the quotes "").
Then I restarted the cloud management and destroyed the SSVM.

The new SSVM tries to download again "".

This still fails and when I look at the Management Log, it looks like there is still no Proxy
2012-11-20 06:44:31,438 DEBUG [agent.transport.Request] (Timer-4:null) Seq 18-550436874: Sending
 { Cmd , MgmtId: 345051959742, via: 18, Ver: v1, Flags: 100011, [{"storage.DownloadProgressCommand":{"jobId":"38d18cba-470a-46da-821d-37cfacd2bb40","request":"GET_STATUS","hvm":false,"description":"CentOS
5.6(64-bit) no GUI (XenServer)","checksum":"905cec879afd9c9d22ecc8036131a180","maxDownloadSizeInBytes":53687091200,"id":5,"resourceType":"TEMPLATE","url":"","format":"VHD","accountId":1,"name":"centos56-x86_64-xen","secUrl":"nfs://","wait":0}}]
2012-11-20 06:44:31,485 DEBUG [agent.transport.Request] (AgentManager-Handler-2:null) Seq
18-550436874: Processing:  { Ans: , MgmtId: 345051959742, via: 18, Ver: v1, Flags: 10, [{"storage.DownloadAnswer":{"jobId":"38d18cba-470a-46da-821d-37cfacd2bb40","downloadPct":0,"errorString":"
","wait":0}}] }

Looks like the Global Setting information is NOT applied :-(

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