Landscape Client

Handle no_proxy configuration setting

Bug #827997 reported by Andreas Hasenack
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Landscape Client
Invalid
Medium
Unassigned
landscape-client (Juju Charms Collection)
Triaged
Medium
Unassigned

Bug Description

A no_proxy configuration setting would accept a list of domains, comma separated, for which no proxy should be used. It's honored by curl, and there is also an env variable with the same name ("no_proxy") that has the same meaning and syntax.

For example, using just env vars and smart (which also uses curl: https://pastebin.canonical.com/51226/

Dean Henrichsmeyer (dean)
Changed in landscape-client:
importance: Undecided → Medium
Revision history for this message
🤖 Landscape Builder (landscape-builder) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

Changed in landscape-client:
status: New → Invalid
Andreas Hasenack (ahasenack)
Changed in landscape-client:
status: Invalid → Triaged
Andreas Hasenack (ahasenack)
tags: added: proxy theme-proxy
Adam Collard (adam-collard)
Changed in landscape-client (Juju Charms Collection):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Michael Croft-White (mikec-w) wrote :

No update in > 5 years.

Changed in landscape-client:
status: Triaged → Invalid
Revision history for this message
Philipp Neuhaus (philippunims) wrote :

I encounter the same problem:

On some of my VMs a proxy is needed to access the internet.

But it must not needed to access our on-prem-landscape.

Calling "landscape-config" to register the VM ends in the script asking for Proxy. It automatically fills in the system environments value - no possibility to deny the proxy.

Even calling the script with "--http_proxy="" --https_proxy="" " does not work...

Revision history for this message
Mark Cunningham (mdscunningham) wrote :

As a workaround, you can add the no_proxy configuration as an environment variable within the systemd service configuration for the landscape-client. This can be added directly to the service file, but is likely more convenient to be added to an override.conf. This can be done with the following command, and adding the additional content shown below to the override.conf file.

sudo systemctl edit landscape-client.service

# Content to add to the override.conf file.

[Service]
Environment=no_proxy=landscape.yourdomain.com

# Then restart the landscape-client.service and try the registration again.

sudo systemctl restart landscape-client.service

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.