environment: trusty
machines:
"0":
agent-state: started
agent-version: 1.16.5
dns-name: test-05.os.magners.qa.lexington
instance-id: /MAAS/api/1.0/nodes/node-1fece8ca-b844-11e2-91a5-d4bed9a84493/
series: trusty
containers:
0/lxc/0:
agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-0/config
/etc/lxc/auto/juju-machine-0-lxc-0.conf: no such file or directory)'
instance-id: pending
series: trusty
0/lxc/1:
agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-1/config
/etc/lxc/auto/juju-machine-0-lxc-1.conf: no such file or directory)'
instance-id: pending
series: trusty
0/lxc/2:
agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-2/config
/etc/lxc/auto/juju-machine-0-lxc-2.conf: no such file or directory)'
instance-id: pending
series: trusty
0/lxc/3:
agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-3/config
/etc/lxc/auto/juju-machine-0-lxc-3.conf: no such file or directory)'
instance-id: pending
series: trusty
0/lxc/4:
agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-4/config
/etc/lxc/auto/juju-machine-0-lxc-4.conf: no such file or directory)'
instance-id: pending
series: trusty
0/lxc/5:
agent-state-info: '(error: symlink /var/lib/lxc/juju-machine-0-lxc-5/config
/etc/lxc/auto/juju-machine-0-lxc-5.conf: no such file or directory)'
instance-id: pending
series: trusty
I think that autostart configuration has changed - reading from lxc-autostart:
DESCRIPTION
lxc-autostart processes containers with lxc.start.auto set. It lets the user start, shutdown, kill, restart containers in the right order, wait‐
ing the right time. Supports filtering by lxc.group or just run against all defined containers. It can also be used by external tools in list
mode where no action will be performed and the list of affected containers (and if relevant, delays) will be shown.
so instead of creating symlinks, the lxc.start.auto configuration should be set.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: juju-core 1.17.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Thu Jan 23 13:49:09 2014
Dependencies:
gcc-4.8-base 4.8.2-14ubuntu2
libc6 2.18-0ubuntu6
libgcc1 1:4.8.2-14ubuntu2
libgo4 4.8.2-14ubuntu2
multiarch-support 2.18-0ubuntu6
ProcEnviron:
TERM=screen-bce
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)
<thumper> hallyn: has the autostart behaviour for lxc changed in trusty?
<hallyn> thumper: yes, stgraber's new autostart setup may be in now. certainly in the ppa
<stgraber> hallyn: yep, it landed with beta2 last week
<thumper> hallyn: hmm... managed to break juju's behaviour
<thumper> hallyn: can you explain the change?
<hallyn> juju uses autostart?
<stgraber> thumper: yes, autostart settings are now upstream and use the container's config instead
<thumper> hallyn: yep,
<stgraber> thumper: I believe I already told someone this morning wrt juju
<stgraber> thumper: use "lxc.start.auto = 1" in the container config
<thumper> stgraber: don't expect us to talk to each other :-)
<hallyn> stgraber: remind me, is there any attempt at auto-conversion for /etc/lxc/auto/ users?
<stgraber> hallyn: yes, there's migration code, but it won't do them much good for new juju containers
<hallyn> heh yah
<stgraber> any container on the system at the time of the upgrade to beta2 should have been automatically converted (symlink removed, /etc/lxc/auto removed and lxc.start.auto = 1 added to the container config)
<thumper> stgraber: is this lxc going into the cloud archive?
<thumper> stgraber: for precise?
<thumper> is there a way we can work out if this is supported?
<stgraber> thumper: maybe hallyn knows, I usually ignore the existence of that external archive entirely
-*- thumper nods
<stgraber> thumper: rule of thumb would be, if /etc/lxc/auto exists, use it, if not, use lxc.start.auto = 1
<thumper> stgraber: that makes sense...
<thumper> should be able to handle that pretty easily