snap proxy settings are not updated

Bug #1690539 reported by Krassi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Tim Penhey

Bug Description

This is a follow-up bug for https://bugs.launchpad.net/juju/+bug/1666353

I am using the newest Juju release (2.2-beta4) and it seems that the proxy settings are still not applied globally. This results in errors when trying to deploy the kubernetes-core bundle, as the snap service cannot reach search.apps.ubuntu.com.

It seems that it was decided against writing the settings to /etc/systemd/{system,user}.conf.d/juju-proxy.conf (although the commit message says otherwise), but even if I follow the instructions and manually create the needed symlinks for each machine (and restart the service) - the snaps still cannot be downloaded.

Looking into the snap.d configuration, it seems that it uses /etc/environment as environment file and as soon as I manually configure the proxy settings there and restart the snappy daemon, then everything works as expected.

Revision history for this message
Menno Finlay-Smits (menno.smits) wrote :

I'm highlighting this to the developer which worked on this.

Changed in juju:
importance: Undecided → High
status: New → Triaged
Tim Penhey (thumper)
summary: - Proxy settings are not set globally
+ snap proxy settings are not updated
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Tim Penhey (thumper)
milestone: none → 2.4.1
Tim Penhey (thumper)
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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