[Starlingx-discuss] [Containers] system application-apply fails to reach 192.168.204.2:9001 when a proxy is set

[Qi, Mingyuan]

Erich,

192.168.204.2 will be automatically added to NO_PROXY after the proxy patch[0] get merged.
Before that, 192.168.204.2 should be added manually, I'll update wiki today in case someone is trying to do a deployment with proxy before the patch merged.

[0] https://review.openstack.org/#/c/633146

Mingyuan

-----Original Message-----
From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] 
Sent: Tuesday, January 29, 2019 2:06
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] [Containers] system application-apply fails to reach 192.168.204.2:9001 when a proxy is set

Hi all, 

I create this bug: https://bugs.launchpad.net/starlingx/+bug/1813635 

I'm seeing an issue on system application-apply stx-openstack when a proxy is set, is unable to reach http://192.168.204.2:9001 and fails due to a timeout. 

The complete logs are in the launchpad.

I changed the proxy configuration to this: 
[Service]
Environment="HTTP_PROXY=http://myproxy" "HTTPS_PROXY=http://myproxy" "NO_PROXY=127.0.0.1,192.168.204.2"

Where I put IP in the NO_PROXY, by this way I can download the images from the external registry. 

This is not the issue I reported this morning in the meeting, but it might be related. 

-Erich

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss