There is a cronjob that runs /opt/canonical/landscape/scripts/update_security_db.sh every hour, and it expects /opt/canonical/landscape/scripts/landscape-env.sh to configure http_proxy and https_proxy env vars if needed.
However, landscape-env.sh expects such vars to be already set in /etc/environment or already part of the shell env.
I would expect landscape-server charm to configure http_proxy and https_proxy via:
1) juju's http-proxy and https-proxy env vars, or
2) a config parameter within landscape-server charm
Please let me know if you'd need further information.
There is a cronjob that runs /opt/canonical/ landscape/ scripts/ update_ security_ db.sh every hour, and it expects /opt/canonical/ landscape/ scripts/ landscape- env.sh to configure http_proxy and https_proxy env vars if needed.
However, landscape-env.sh expects such vars to be already set in /etc/environment or already part of the shell env.
I would expect landscape-server charm to configure http_proxy and https_proxy via:
1) juju's http-proxy and https-proxy env vars, or
2) a config parameter within landscape-server charm
Please let me know if you'd need further information.