MAAS does not set snap proxy

Bug #1918997 reported by Lee Trager
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Alberto Donato

Bug Description

I am working in an environment with limited network access. MAAS properly configures apt to use a proxy however it is not configuring the Snap proxy. There may be a way to do this with cloud-init but the following enabled snap to use the MAAS proxy

snap set system proxy.http="http://10-0-1-0--24.maas-internal:8000/"
snap set system proxy.https="http://10-0-1-0--24.maas-internal:8000/"

Related branches

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Indeed I confirm i have experienced the same.

In cloud-config speak "snap *" are just a series of commands that cloud-init can execute.

https://cloudinit.readthedocs.io/en/latest/topics/modules.html#snap

See examples there it is very laxed thus one should be able to do above with just:

snap:
  commands:
    - snap set system proxy.http="http://10-0-1-0--24.maas-internal:8000/"
    - snap set system proxy.https="http://10-0-1-0--24.maas-internal:8000/"

Alberto Donato (ack)
Changed in maas:
milestone: none → 2.10.0
Alberto Donato (ack)
Changed in maas:
assignee: nobody → Alberto Donato (ack)
status: Triaged → In Progress
status: In Progress → Triaged
assignee: Alberto Donato (ack) → nobody
Alberto Donato (ack)
Changed in maas:
status: Triaged → In Progress
assignee: nobody → Alberto Donato (ack)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 3.0.0 → 3.0-beta1
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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