Thanks for digging into this so much, Martin! 1 - Yes, I will try the runcmd you mention and see if it works.
2 - However, I thought adding in After=cloud-config.target would ensure that it wouldn't start until after cloud-init completes? 3 - The recreate steps for this are: - Bootstrap local env on wily (this won't create a container) - Deploy using the command: `juju deploy wily/ubuntu`. It may take some time before you see the container started as juju will download the image before starting the template container. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1509747 Title: Intermittent lxc failures on wily, juju-template-restart.service race condition Status in juju-core: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Frequently, when creating an lxc container on wily (either through --to lxc:#, or using the local provider on wily), the template never stops and errors out here: [ 2300.885573] cloud-init[2758]: Cloud-init v. 0.7.7 running 'modules:final' at Sun, 25 Oct 2015 00:28:57 +0000. Up 182 seconds. [ 2300.886101] cloud-init[2758]: Cloud-init v. 0.7.7 finished at Sun, 25 Oct 2015 00:29:03 +0000. Datasource DataSourceNoCloudNet [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]. Up 189 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Started /dev/initctl Compatibility Daemon. [FAILED] Failed to start Update UTMP about System Runlevel Changes. See 'systemctl status systemd-update-utmp-runlevel.service' for details. Attaching to the container and running the above command yields: ubuntu@cherylj-wily-local-lxc:~$ sudo lxc-attach --name juju-wily-lxc-template root@juju-wily-lxc-template:~# systemctl status systemd-update-utmp-runlevel.service ● systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel Changes Loaded: loaded (/lib/systemd/system/systemd-update-utmp-runlevel.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2015-10-25 00:30:29 UTC; 2h 23min ago Docs: man:systemd-update-utmp.service(8) man:utmp(5) Process: 3963 ExecStart=/lib/systemd/systemd-update-utmp runlevel (code=exited, status=1/FAILURE) Main PID: 3963 (code=exited, status=1/FAILURE) Oct 25 00:29:46 juju-wily-lxc-template systemd[1]: Starting Update UTMP about System Runlevel Changes... Oct 25 00:30:29 juju-wily-lxc-template systemd[1]: systemd-update-utmp-runlevel.service: Main process exited, code=exited, status=1/FAILURE Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: Failed to start Update UTMP about System Runlevel Changes. Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: systemd-update-utmp-runlevel.service: Unit entered failed state. Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: systemd-update-utmp-runlevel.service: Failed with result 'exit-code'. I have seen this on ec2 and in canonistack. The canonistack machine is available for further debugging. Ping me for access. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
