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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509747 Title: Intermittent lxc failures on wily, juju-template-restart.service race condition To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
