lxd-agent and cloud-init-local issues about lxd HOT 6 OPEN

Confirmed. running an image from ubuntu: shows the correct start order of services

from lxd.

in the above syslog shows an entry made by lxd-agent 2s after lxd-agent

Please could you elaborate what you mean by:

by lxd-agent 2s after lxd-agent

Do you mean the 1s gap between log messages?

Or do you mean its happening after cloud-init?

from lxd.

in the above syslog shows an entry made by lxd-agent 2s after lxd-agent

Please could you elaborate what you mean by:

by lxd-agent 2s after lxd-agent

Do you mean the 1s gap between log messages?

Or do you mean its happening after cloud-init?

The log entries are a symptom of the problem, so unimportant, sorry for the confusion

I found that lxd-agent starts after cloud-init-local despite the entry in /usr/lib/systemd/system/lxd-agent.service

...
Before=multi-user.target cloud-init.target cloud-init.service cloud-init-local.service
...

So the issue is specific to the image, which is built from Ubuntu cloud images but via packer.

Any suggestions as to how this might happen?

from lxd.

Thanks.

So it doesn't happen with the ubuntu: remote images?

from lxd.

Please can you share how you are building the image?

from lxd.

packer -> ansible -> qcow2 -> lxc image import

from lxd.