apt-mirror is not used in containers with MAAS provider

Bug #1560391 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Cheryl Jennings
juju-core
Fix Released
High
Cheryl Jennings
1.25
Fix Released
High
Cheryl Jennings

Bug Description

With MAAS 1.9 and juju-core 1.25.3, local mirror won't be used in containers even setting apt-mirror in environments.yaml

1. bootstrap with "apt-mirror: http://mylocalmirror.example.com/ubuntu" in environments.yaml
2. create a container with `juju add-machine lxc:0`
3. check /etc/apt/sources.list in the container

/etc/apt/sources.list still has "archive.ubuntu.com" not my local mirror.

Revision history for this message
Cheryl Jennings (cherylj) wrote :

Yeah, I can see that the AptMirror is not populated by ContainerConfig() in the provisioner API.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.25.5
Changed in juju-core:
milestone: 1.25.5 → 2.0-beta4
Revision history for this message
Cheryl Jennings (cherylj) wrote :
Revision history for this message
Cheryl Jennings (cherylj) wrote :
Changed in juju-core:
status: Triaged → In Progress
assignee: nobody → Cheryl Jennings (cherylj)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta4 → none
milestone: none → 2.0-beta4
Changed in juju-core:
assignee: nobody → Cheryl Jennings (cherylj)
importance: Undecided → High
status: New → 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.