snap proxy settings are not updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Tim Penhey |
Bug Description
This is a follow-up bug for https:/
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.
It seems that it was decided against writing the settings to /etc/systemd/
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.
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 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
I'm highlighting this to the developer which worked on this.