proxy is not used in ephemeral or commissioning
Bug #1066020 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Raphaël Badin | ||
1.2 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
the apt proxy is not sent down to either ephemeral environment or commissioning environment.
ephemeral is as easy as un-commenting the line in the template (preseeds/
apt_proxy: http://{{server_
commissioning is more tricky as we dont have any rendered content there at all.
We should change the way we build that user-data so we can have a cloud-config part htat does this.
(which would also help with commissioning scripts).
Related branches
lp://staging/~rvb/maas/use-proxy
- Julian Edwards (community): Approve
-
Diff: 111 lines (+40/-7)4 files modifiedcontrib/preseeds_v2/generic (+4/-0)
src/maasserver/forms.py (+3/-1)
src/maasserver/preseed.py (+1/-0)
src/maasserver/tests/test_preseed.py (+32/-6)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in maas: | |
assignee: | nobody → Raphaël Badin (rvb) |
tags: | added: feature |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Just for conveience of people hitting this, here is a patch demonstrating what you can do to a running maas to get this fixed.
I'd like to re-work how commissioning rendering is done, and clearly we have to have access to some variables such as the squid proxy to do this correctly.
However, see the stop gap fix here.