Comment 15 for bug 2025978

For the record: using the legacy proxy settings seems to allow for a clean deploy. However, if I then try to deploy landscape-client, the proxy settings seem to get in the way. It appears the environment-level proxy settings are then stored in /etc/landscape/client.conf (without any "no-proxy"-type setting), and this ends up breaking things when that proxy shouldn't be used to reach landscape. I also then have to manually edit the /etc/landscape/client.conf files to remove such proxy references in order for registration to succeed.

On the other hand, the juju-*-proxy settings do not result in such config settings in the landscape-client charm.

Long story short: the current implementation is problematic if the customer requires a proxy for external access, yet the proxy shouldn't be used for accessing landscape via landscape-client. If we could avoid needing to use the legacy proxy settings, it would help.