landscape-env.sh should source /etc/juju-proxy.conf, if present

[David Coronel]

The landscape-server charm doesn't have support for proxy server options.

Configuring the proxy server on Landscape servers seems to involve modifying the /etc/environment file to add HTTP_PROXY/HTTPS_PROXY/http_proxy/https_proxy and no_proxy/NO_PROXY environment variables but there is no viable way to do this in a Juju environment.

Additionally, if there is a proxy configured in /etc/environment, the update_db_security.sh will fail if there is not a NO_PROXY/no_proxy variable configured to exclude 127.0.0.1 and localhost.

I think the landscape-server charm should have a proxy option similar to the canonical-livepatch charm and handle this proxy configuration accordingly (/etc/environment or other (directly in the update_db_security.sh script, etc.).

This is with the latest landscape-server charm revision 36.

[David Coronel (davecore)]

subscribed ~field-medium

[David Coronel (davecore)]

My workaround is to manually add the proxy and no_proxy variables to /etc/environment and restart Landscape

[David Coronel (davecore)]

Further investigation (thank you Simon) indicates that Juju sets the model proxy options (juju-http-proxy and juju-https-proxy) get set in profile.d. Many things use profile.d but not cron.

That would explain why the update_db_security.sh script ran from cron doesn't take the proxy server into consideration.

One workaround could still be to set the HTTP_PROXY/HTTPS_PROXY/http_proxy/https_proxy and no_proxy/NO_PROXY environment variables in /etc/environment on the Landscape leader unit (since only that unit run the cron jobs (since only that unit has RUN_CRON set to true in /etc/default/landscape-server)).