Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Wed, 13 Feb 2013 23:42:12 +0000 (UTC)
From: "Chris Portman (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <JIRA.12616945.1353423191465.286903.1360798932722@arcas>
In-Reply-To: <JIRA.12616945.1353423191465@arcas>
References: <JIRA.12616945.1353423191465@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-524) http proxy used by ssvm
 (secstorage.proxy) NOT working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578038#comment-13578038 ] 

Chris Portman commented on CLOUDSTACK-524:
------------------------------------------

Hi,

Just wondering if there has been any progress on this.  I have set the secstorage.proxy global and restarted the management service, restarted the svvm service and the ssvm machine and even resorted to destroying the svvm and allowing it to be rebuilt.  The option is not taking effect.  A tcpdump show the svvm is trying to go directly to the server hosting the ISOs on port 80 rather than to the proxy server.

I have also tried the suggestion above regarding the Java options by adding -Dhttp.proxyHost=<proxy ip> -Dhttp.proxyPort=3128 to the last line in /usr/local/cloud/systemvm/_run.sh to no avail.

It also appears that it takes no notice of the http_proxy env var (added through the use of /etc/profile and a reboot).

Any help would be greatly appreciated.

Thanks.
Chris
                
> http proxy used by ssvm (secstorage.proxy) NOT working
> ------------------------------------------------------
>
>                 Key: CLOUDSTACK-524
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-524
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          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 "http://proxy.xyz.com:3128" (without the quotes "").
> Then I restarted the cloud management and destroyed the SSVM.
> The new SSVM tries to download again "http://download.cloud.com/templates/builtin/centos56-x86_64.vhd.bz2".
> This still fails and when I look at the Management Log, it looks like there is still no Proxy used:
> 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":"http://download.cloud.com/templates/builtin/centos56-x86_64.vhd.bz2","format":"VHD","accountId":1,"name":"centos56-x86_64-xen","secUrl":"nfs://10.30.1.3/export/secondary","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":" ","downloadStatus":"NOT_DOWNLOADED","downloadPath":"/mnt/SecStorage/ff53ffad-7c5d-382f-942c-e527528c5699/template/tmpl/1/5/dnld5122201514511320578tmp_","templateSize":0,"templatePhySicalSize":0,"checkSum":"905cec879afd9c9d22ecc8036131a180","result":false,"details":" ","wait":0}}] }
> Conclusion;
> 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: http://www.atlassian.com/software/jira