Merge lp:~thumper/juju-core/local-provider-machines-no-lxc into lp:~go-bot/juju-core/trunk
Status: | Merged |
---|---|
Approved by: | Tim Penhey |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2021 |
Proposed branch: | lp:~thumper/juju-core/local-provider-machines-no-lxc |
Merge into: | lp:~go-bot/juju-core/trunk |
Diff against target: |
11 lines (+1/-0) 1 file modified
provider/local/environ.go (+1/-0) |
To merge this branch: | bzr merge lp:~thumper/juju-core/local-provider-machines-no-lxc |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+193848@code.launchpad.net |
Commit message
Fix local provider again.
The cloud-init data for local provider machines was
trying to install lxc. This has been avoided as a
container due to the problem with nested lxc and the
default profiles in precise.
The fact that lxc was being installed on these machines
was an oversight, and one that is now biting us due to
a change to cgroups-lite which is triggering apparmor
to complain. This leaves apt in a partial install state
so while the agent itself will start, all install hooks
fail.
The solution is to specify in the machine config that
the container type is LXC. This stops LXC from being
added to the package list to install.
Description of the change
Fix local provider again.
The cloud-init data for local provider machines was
trying to install lxc. This has been avoided as a
container due to the problem with nested lxc and the
default profiles in precise.
The fact that lxc was being installed on these machines
was an oversight, and one that is now biting us due to
a change to cgroups-lite which is triggering apparmor
to complain. This leaves apt in a partial install state
so while the agent itself will start, all install hooks
fail.
The solution is to specify in the machine config that
the container type is LXC. This stops LXC from being
added to the package list to install.
Reviewers: mp+193848_ code.launchpad. net,
Message:
Please take a look.
Description:
Fix local provider again.
The cloud-init data for local provider machines was
trying to install lxc. This has been avoided as a
container due to the problem with nested lxc and the
default profiles in precise.
The fact that lxc was being installed on these machines
was an oversight, and one that is now biting us due to
a change to cgroups-lite which is triggering apparmor
to complain. This leaves apt in a partial install state
so while the agent itself will start, all install hooks
fail.
The solution is to specify in the machine config that
the container type is LXC. This stops LXC from being
added to the package list to install.
https:/ /code.launchpad .net/~thumper/ juju-core/ local-provider- machines- no-lxc/ +merge/ 193848
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/21740043/
Affected files (+3, -0 lines): local/environ. go
A [revision details]
M provider/
Index: [revision details] 20131104055758- 320vn2wsihe9ky8 z
=== added file '[revision details]'
--- [revision details] 2012-01-01 00:00:00 +0000
+++ [revision details] 2012-01-01 00:00:00 +0000
@@ -0,0 +1,2 @@
+Old revision: tarmac-
+New revision: <email address hidden>
Index: provider/ local/environ. go local/environ. go' local/environ. go 2013-10-31 21:27:57 +0000 local/environ. go 2013-11-04 21:09:23 +0000 OneSeries( ) Debugf( "StartInstance: %q, %s", machineConfig. MachineId, series) g.Tools = possibleTools[0] MachineContaine rType = instance.LXC Debugf( "tools: %#v", machineConfig. Tools) rkConfig( env.config. networkBridge( )) FinishMachineCo nfig(machineCon fig, env.config.Config,
=== modified file 'provider/
--- provider/
+++ provider/
@@ -264,6 +264,7 @@
series := possibleTools.
logger.
machineConfi
+ machineConfig.
logger.
network := lxc.BridgeNetwo
if err := environs.
cons); err != nil {