ComposeUserData provides no mechanism for customising apt options
Bug #1295058 reported by
Andrew Wilkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Low
|
Andrew Wilkins |
Bug Description
We've got environs.
In the MAAS provider we need to also do an apt-get update && apt-get install bridge-utils during bootstrap. This is necessary so that we restart networking before the synchronous bootstrap phase begins. Ideally we would just set the appropriate options on cloudinit.Config directly, but instead we're currently stuck with adding runcmds.
Related branches
lp://staging/~axwalk/juju-core/composeuserdata-customise-cloudinit
- Juju Engineering: Pending requested
-
Diff: 291 lines (+52/-70)11 files modifiedenvirons/cloudinit.go (+18/-17)
environs/cloudinit_test.go (+5/-2)
provider/azure/customdata.go (+1/-1)
provider/azure/customdata_test.go (+1/-1)
provider/ec2/ec2.go (+1/-1)
provider/maas/environ.go (+16/-12)
provider/maas/environ_test.go (+6/-6)
provider/maas/export_test.go (+3/-3)
provider/openstack/provider.go (+1/-1)
utils/apt.go (+0/-10)
utils/apt_test.go (+0/-16)
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
milestone: | none → 1.18.0 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
milestone: | 1.18.0 → 1.17.7 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.