snap-http-proxy and snap-https-proxy not honored in juju 2.4.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snap Layer |
Fix Released
|
High
|
Unassigned | ||
juju-core |
Invalid
|
Undecided
|
Unassigned |
Bug Description
In an environment where I must proxy all APT and snapstore traffic through my MAAS node (10.216.2.0/16), I've set up the juju model-config on juju 2.4.1 to set snap-http-proxy and snap-https-proxy to http://
Unit error log snippet: https:/
Model-config: https:/
However, if I set http-proxy and https-proxy in my model, restart snapd on the affected unit and then re-run the install hook succeeds.
This either is my misunderstanding of what snap-http-proxy is supposed to provide (assumed it was access to the store) or the functionality is not working as intended because the charm is overriding it with it's own snap-proxy settings that are blank.
Should this juju model snap-http-proxy config override the charm's settings of such?
Changed in juju-core: | |
status: | New → Incomplete |
Changed in juju-core: | |
status: | Incomplete → Invalid |
Changed in layer-snap: | |
status: | Incomplete → Triaged |
Changed in layer-snap: | |
importance: | Undecided → High |
Changed in layer-snap: | |
status: | Triaged → Fix Released |
I'm guessing that this charm being layer-etcd, that it's using layer-apt which would possibly be intermingling settings from the charm configs and juju model.