lxc nested within kvm machines do not use lxc-clone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
1.18 |
Fix Released
|
High
|
Andrew Wilkins | ||
juju-core (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
When deploying services within an LXC nested in a KVM machine the lxc-clone support is not used.
[Test Case]
status output:
environment: local
machines:
"0":
agent-state: started
agent-version: 1.18.1.1
dns-name: localhost
instance-id: localhost
series: trusty
"1":
agent-state: started
agent-version: 1.18.1.1
dns-name: 10.0.3.129
instance-id: poe-local-machine-1
series: trusty
containers:
1/lxc/0:
series: precise
hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
services:
wordpress:
charm: cs:precise/
exposed: false
relations:
loadbalancer:
- wordpress
units:
wordpress/0:
machine: 1/lxc/0
lxc-ls output from the kvm machine
ubuntu@ubuntu:~$ sudo lxc-ls --fancy
NAME STATE IPV4 I PV6 AUTOSTART
-------
juju-machine-
No juju-trusty-
[Regression Potentional]
This only applies to new bootstrapped environments with lxc-use-clone applied. Existing environments will continue unaffected.
Thanks
Adam
Related branches
- Juju Engineering: Pending requested
-
Diff: 406 lines (+156/-15)12 files modifiedenvirons/config/config.go (+13/-3)
environs/config/config_test.go (+6/-0)
state/api/params/params.go (+12/-0)
state/api/provisioner/provisioner.go (+8/-1)
state/api/provisioner/provisioner_test.go (+54/-0)
state/apiserver/provisioner/provisioner.go (+20/-1)
state/apiserver/provisioner/provisioner_test.go (+10/-0)
worker/provisioner/container_initialisation.go (+19/-3)
worker/provisioner/kvm-broker.go (+2/-1)
worker/provisioner/kvm-broker_test.go (+5/-2)
worker/provisioner/lxc-broker.go (+2/-2)
worker/provisioner/lxc-broker_test.go (+5/-2)
- Juju Engineering: Pending requested
-
Diff: 407 lines (+157/-14)12 files modifiedenvirons/config/config.go (+12/-2)
environs/config/config_test.go (+6/-0)
state/api/params/params.go (+12/-0)
state/api/provisioner/provisioner.go (+8/-1)
state/api/provisioner/provisioner_test.go (+54/-0)
state/apiserver/provisioner/provisioner.go (+22/-1)
state/apiserver/provisioner/provisioner_test.go (+10/-0)
worker/provisioner/container_initialisation.go (+19/-3)
worker/provisioner/kvm-broker.go (+2/-1)
worker/provisioner/kvm-broker_test.go (+5/-2)
worker/provisioner/lxc-broker.go (+2/-2)
worker/provisioner/lxc-broker_test.go (+5/-2)
tags: | added: cloud-installer kvm local-provider lxc |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in juju-core: | |
milestone: | none → 1.18.3 |
milestone: | 1.18.3 → 1.19.2 |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in juju-core (Ubuntu Trusty): | |
status: | Confirmed → Fix Released |
Curtis,
Could we get the importance set higher? Without lxc cloning support in kvm instances deploy times can take a significantly longer amount of time (upwards of 30minutes to deploy openstack)
Thanks
Adam