Activity log for bug #1315216

Date Who What changed Old value New value Message
2014-05-02 02:21:33 Adam Stokes bug added bug
2014-05-02 02:21:50 Adam Stokes tags cloud-installer kvm local-provider lxc
2014-05-02 17:00:40 Curtis Hovey juju-core: status New Triaged
2014-05-02 17:00:43 Curtis Hovey juju-core: importance Undecided Low
2014-05-03 10:37:21 Ian Booth juju-core: importance Low High
2014-05-08 11:10:57 Ian Booth juju-core: milestone 1.18.3
2014-05-08 11:11:11 Ian Booth juju-core: milestone 1.18.3 1.19.2
2014-05-08 13:09:04 Curtis Hovey bug added subscriber Curtis Hovey
2014-05-08 15:14:51 Curtis Hovey branch linked lp:~axwalk/juju-core/lp1315216-lxc-use-clone
2014-05-08 15:15:01 Curtis Hovey juju-core: status Triaged In Progress
2014-05-08 15:15:17 Curtis Hovey juju-core: assignee Andrew Wilkins (axwalk)
2014-05-09 00:20:45 Ian Booth nominated for series juju-core/1.18
2014-05-09 00:20:45 Ian Booth bug task added juju-core/1.18
2014-05-09 00:20:55 Ian Booth juju-core/1.18: milestone 1.18.3
2014-05-09 00:21:08 Ian Booth juju-core/1.18: assignee Andrew Wilkins (axwalk)
2014-05-09 00:21:13 Ian Booth juju-core/1.18: importance Undecided High
2014-05-09 00:21:19 Ian Booth juju-core/1.18: status New In Progress
2014-05-09 02:30:54 Andrew Wilkins juju-core: status In Progress Fix Committed
2014-05-09 03:58:44 Andrew Wilkins branch linked lp:~axwalk/juju-core/lp1315216-lxc-use-clone-1.18
2014-05-09 04:35:05 Andrew Wilkins juju-core/1.18: status In Progress Fix Committed
2014-05-09 17:25:24 Canonical Juju QA Bot juju-core/1.18: status Fix Committed Fix Released
2014-05-11 01:37:40 Canonical Juju QA Bot juju-core: status Fix Committed Fix Released
2014-05-12 20:21:05 Adam Stokes bug task added juju-core (Ubuntu)
2014-05-12 20:21:17 Adam Stokes nominated for series Ubuntu Trusty
2014-05-12 20:21:17 Adam Stokes bug task added juju-core (Ubuntu Trusty)
2014-05-12 20:21:27 Adam Stokes juju-core (Ubuntu): importance Undecided High
2014-05-12 20:21:31 Adam Stokes juju-core (Ubuntu Trusty): importance Undecided High
2014-05-12 20:21:37 Adam Stokes juju-core (Ubuntu): status New Confirmed
2014-05-12 20:21:41 Adam Stokes juju-core (Ubuntu Trusty): status New Confirmed
2014-05-12 20:22:32 Adam Stokes juju-core (Ubuntu): milestone ubuntu-14.04.1
2014-05-12 20:22:45 Adam Stokes juju-core (Ubuntu): milestone ubuntu-14.04.1
2014-05-12 20:22:49 Adam Stokes juju-core (Ubuntu Trusty): milestone ubuntu-14.04.1
2014-05-12 20:25:28 Adam Stokes description When deploying services within an LXC nested in a KVM machine the lxc-clone support is not used. 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: instance-id: pending series: precise hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M services: wordpress: charm: cs:precise/wordpress-21 exposed: false relations: loadbalancer: - wordpress units: wordpress/0: agent-state: pending 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-1-lxc-0 RUNNING 10.0.3.105 - NO No juju-trusty-template is ever defined for re-use. Thanks Adam [Impact] Users wishing to use nested lxc containers will benefit from the additional speed that cloning provides. [Test Case] When deploying services within an LXC nested in a KVM machine the lxc-clone support is not used. 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:         instance-id: pending         series: precise     hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M services:   wordpress:     charm: cs:precise/wordpress-21     exposed: false     relations:       loadbalancer:       - wordpress     units:       wordpress/0:         agent-state: pending         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-1-lxc-0 RUNNING 10.0.3.105 - NO No juju-trusty-template is ever defined for re-use. [Regression Potentional] This only applies to new bootstrapped environments with lxc-use-clone applied. Existing environments will continue unaffected. Thanks Adam
2014-05-12 20:25:44 Adam Stokes description [Impact] Users wishing to use nested lxc containers will benefit from the additional speed that cloning provides. [Test Case] When deploying services within an LXC nested in a KVM machine the lxc-clone support is not used. 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:         instance-id: pending         series: precise     hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M services:   wordpress:     charm: cs:precise/wordpress-21     exposed: false     relations:       loadbalancer:       - wordpress     units:       wordpress/0:         agent-state: pending         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-1-lxc-0 RUNNING 10.0.3.105 - NO No juju-trusty-template is ever defined for re-use. [Regression Potentional] This only applies to new bootstrapped environments with lxc-use-clone applied. Existing environments will continue unaffected. Thanks Adam [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:         instance-id: pending         series: precise     hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M services:   wordpress:     charm: cs:precise/wordpress-21     exposed: false     relations:       loadbalancer:       - wordpress     units:       wordpress/0:         agent-state: pending         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-1-lxc-0 RUNNING 10.0.3.105 - NO No juju-trusty-template is ever defined for re-use. [Regression Potentional] This only applies to new bootstrapped environments with lxc-use-clone applied. Existing environments will continue unaffected. Thanks Adam
2015-04-06 19:49:19 Curtis Hovey juju-core (Ubuntu): status Confirmed Fix Released
2015-04-06 19:49:22 Curtis Hovey juju-core (Ubuntu Trusty): status Confirmed Fix Released