Looking through the logs in comment 8 for any indications of restarts, unloads, I came up with this interesting discrepancy. Basically the failure is recorded as happening 37s before the profile is loaded.
The load message for the container's profile Feb 18 14:06:11 elkhart kernel: [ 494.893832] audit: type=1400 audit(1487426771 .526:110): apparmor="STATUS" operation="profile_load" profile="unconfined" name= "lxd-juju-2c21a7-1-lxd-4_</var/lib/lxd>" pid=54569 comm="apparmor_parser" the failure message from juju for the containers profile. 2017-02-18 14:05:34 WARNING juju.provisioner provisioner_task.go:739 failed to s tart instance (Error calling 'lxd forkstart juju-2c21a7-1-lxd-4 /var/lib/lxd/con tainers /var/log/lxd/juju-2c21a7-1-lxd-4/lxc.conf': err='exit status 1' lxc 20160218140528.391 ERROR lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:234 - No such file or directory - failed to change apparmor profile to lxd-juju-2c21a7-1-lxd-4_</var/lib/lxd>//&:lxd-juju-2c21a7-1-lxd-4_<var-lib-lxd>: lxc 20160218140528.391 ERROR lxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 5) lxc 20160218140528.391 ERROR lxc_start - start.c:__lxc_start:1346 - Failed to spawn container "juju-2c21a7-1-lxd-4". lxc 20160218140528.986 ERROR lxc_conf - conf.c:run_buffer:405 - Script exited with status 1. lxc 20160218140528.986 ERROR lxc_start - start.c:lxc_fini:546 - Failed to run lxc.hook.post-stop for container "juju-2c21a7-1-lxd-4". ), retrying in 10s (3 more attempts) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667444 Title: Failed to start lxd container because it is already running a start operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1667444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
