JFYI, the host where juju bootstrap was run, the proxy is configured via /etc/environment, so the juju client should have access to the internet.
$ env | grep -i proxy no_proxy=localhost,127.0.0.1,<IP_ADDRESES> https_proxy=http://192.168.1.10:8000/ HTTPS_PROXY=http://192.168.1.10:8000/ HTTP_PROXY=http://192.168.1.10:8000/ http_proxy=http://192.168.1.10:8000/
I have attached the full juju bootstrap output with '<root>=TRACE'
As this is hitting customer environment, and have a workaround with the legacy http-proxy configuration. I'm subscribing this to field-high
JFYI, the host where juju bootstrap was run, the proxy is configured via /etc/environment, so the juju client should have access to the internet.
$ env | grep -i proxy localhost, 127.0.0. 1,<IP_ADDRESES> 192.168. 1.10:8000/ 192.168. 1.10:8000/ 192.168. 1.10:8000/ 192.168. 1.10:8000/
no_proxy=
https_proxy=http://
HTTPS_PROXY=http://
HTTP_PROXY=http://
http_proxy=http://
I have attached the full juju bootstrap output with '<root>=TRACE'
As this is hitting customer environment, and have a workaround with the legacy http-proxy configuration.
I'm subscribing this to field-high