@stgraber > What's that environment like? Are all those containers running on the host > directly or are they nested?
These containers are all running directly on the host (an amd64 box). The host is managed by maas with juju driving the deployment and juju creating the lxcs. The host is running 16.04 and the lxcs are all 16.04. I've now found two more cases of this since filing the original bug. The error messages look identical to the original one used to file this bug. The newer cases found in our CI are (note that these are only accessible by the landscape team, I'm including them here for my reference): - https://ci.lscape.net/job/landscape-system-tests/5477 - https://ci.lscape.net/job/landscape-system-tests/5481 Are additional logs needed to debug this? I may be able to catch a live failure if that is required to debug. ** Changed in: lxd (Ubuntu) Status: Incomplete => New -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
