Looks like Juju is attempting to start the container twice. But that's
not really the problem. The problem is that the container start itself
failed.
We'd need all the files from /var/log/lxd/<container name>/ to
investigate. That may be made somewhat difficult by the fact that Juju
appears to clean everything up on failure.
The usual culprit for this is some invalid configuration in the Juju (or
conjure-up) generated profile. Things like missing kernel modules or missing
devices, but without the actual error message for the container in question,
it's hard to tell exactly what's the issue.
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692985
Title:
Juju openstack lvd returns always "Container is already running a
start operation"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1692985/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
