Activity log for bug #1351368

Date Who What changed Old value New value Message
2014-08-01 15:52:42 David Britton bug added bug
2014-08-01 15:53:45 David Britton attachment added machine-0.log https://bugs.launchpad.net/juju-core/+bug/1351368/+attachment/4167477/+files/machine-0.log
2014-08-01 15:58:53 David Britton bug added subscriber Landscape
2014-08-01 15:59:49 David Britton description I'm not sure what is unique about this situation. It's similar to many of the other LXC bugs that have been filed where instances stay in pending indefinitely. But the way it got there is a bit unique: 2014-08-01 15:10:27 ERROR juju.provisioner container_initialisation.go:154 cannot get tools from machine for lxc container 2014-08-01 15:10:27 ERROR juju.provisioner container_initialisation.go:95 starting container provisioner for lxc: initialising container infrastructure on host machine: no matching tools available 2014-08-01 15:10:27 ERROR juju.worker runner.go:218 exited "0-container-watcher": initialising container infrastructure on host machine: no matching tools available Then at the end of the log (not sure if this is important): 2014-08-01 15:11:59 ERROR juju.state.apiserver debuglog.go:101 debug-log handler error: write tcp 172.16.1.98:49085: broken pipe I'll attach the full machine-0.log for details. The end result is that the lxcs do not come up, even the lxc package doesn't get installed. I'm not sure what is unique about this situation. It's similar to many of the other LXC bugs that have been filed where instances stay in pending indefinitely. But the way it got there is a bit unique: 2014-08-01 15:10:27 ERROR juju.provisioner container_initialisation.go:154 cannot get tools from machine for lxc container 2014-08-01 15:10:27 ERROR juju.provisioner container_initialisation.go:95 starting container provisioner for lxc: initialising container infrastructure on host machine: no matching tools available 2014-08-01 15:10:27 ERROR juju.worker runner.go:218 exited "0-container-watcher": initialising container infrastructure on host machine: no matching tools available Then at the end of the log (not sure if this is important): 2014-08-01 15:11:59 ERROR juju.state.apiserver debuglog.go:101 debug-log handler error: write tcp 172.16.1.98:49085: broken pipe I'll attach the full machine-0.log for details. The end result is that the lxcs do not come up, even the lxc package doesn't get installed. Environment: trusty w/ trusty containers, juju 1.20.2 pre-release package.
2014-08-04 14:43:30 Curtis Hovey juju-core: status New Incomplete
2014-08-04 14:43:34 Curtis Hovey juju-core: importance Undecided High
2014-08-04 14:43:39 Curtis Hovey juju-core: milestone 1.20.3
2014-08-04 20:08:06 Ian Booth juju-core: milestone 1.20.3
2014-08-15 16:02:39 David Britton attachment added lxc-error-log https://bugs.launchpad.net/juju-core/+bug/1351368/+attachment/4178576/+files/lxc-error-log
2014-08-15 16:06:47 David Britton juju-core: status Incomplete New
2014-08-15 20:59:41 David Britton attachment added more-log https://bugs.launchpad.net/juju-core/+bug/1351368/+attachment/4178846/+files/more-log
2014-08-18 14:09:44 Curtis Hovey juju-core: status New Triaged
2014-08-18 14:10:27 Curtis Hovey tags cloud-installer landscape cloud-installer landscape lxc
2014-08-19 09:00:25 David Britton attachment added deployer.yaml https://bugs.launchpad.net/juju-core/+bug/1351368/+attachment/4181409/+files/deployer.yaml
2014-08-21 21:58:00 Ryan Harper tags cloud-installer landscape lxc cloud-installer landscape lxc oil
2014-08-21 22:38:36 Patricia Gaughen bug added subscriber Patricia Gaughen
2014-08-22 13:45:47 Curtis Hovey marked as duplicate 1350008
2014-08-25 22:46:14 Ian Booth removed duplicate marker 1350008
2014-08-25 22:46:29 Ian Booth marked as duplicate 1360994
2014-09-02 06:02:50 Ian Booth removed duplicate marker 1360994
2014-09-02 06:03:01 Ian Booth marked as duplicate 1359800