Closed holmanb closed 1 year ago
Anything useful in journalctl -u lxd-agent
?
Anything useful in
journalctl -u lxd-agent
?
I don't see anything
root@myhostname1:~# journalctl -u lxd-agent
Feb 15 17:59:12 myhostname1 systemd[1]: Started LXD - agent.
Feb 15 17:59:24 myhostname1 su[1054]: (to root) root on pts/0
Feb 15 17:59:24 myhostname1 su[1054]: pam_unix(su-l:session): session opened for user root(uid=0) by (uid=0)
-- Boot 18f83c5d2be140b0bdc26ad535127594 --
Feb 15 18:00:19 myhostname1 systemd[1]: Started LXD - agent.
Feb 15 18:01:24 myhostname1 su[1495]: (to root) root on pts/0
Feb 15 18:01:24 myhostname1 su[1495]: pam_unix(su-l:session): session opened for user root(uid=0) by (uid=0)
-- Boot 1f046db33f4540038c84bd1465c398b5 --
Feb 15 18:02:20 myhostname1 systemd[1]: Started LXD - agent.
Feb 15 18:04:36 myhostname1 su[1413]: (to root) root on pts/0
Feb 15 18:04:36 myhostname1 su[1413]: pam_unix(su-l:session): session opened for user root(uid=0) by (uid=0)
-- Boot b1c602c47a5b415c8e76aa1ddb54d857 --
Feb 15 18:54:08 myhostname1 systemd[1]: Started LXD - agent.
-- Boot 28b157f1574a4fc5bd4a40f3efef7d66 --
Feb 18 15:12:53 myhostname1 systemd[1]: Started LXD - agent.
Feb 18 15:17:01 myhostname1 su[1414]: (to root) root on pts/0
Feb 18 15:17:01 myhostname1 su[1414]: pam_unix(su-l:session): session opened for user root(uid=0) by (uid=0)
Okay. @monstermunchkin can you look into this?
Distribution: Ubuntu Distribution version: kinetic / 22.10 The output of "lxc info":
Issue description
I recently discovered on a specific image that cloud-init is querying over
/dev/lxd/sock
too early, which causes cloud-init to fail. What (if any), synchronization method would be best to ensure cloud-init doesn't query too soon? I have an ugly workaround proposed, but it's obviously not a "real" fix.Steps to reproduce
It seems that this might be related to lxd versions, since a coworker wasn't able to reproduce it until they downgraded to 5.0 stable. However I consistently reproduce this issue on 5.10.
lxc launch images:ubuntu/jammy/desktop myhostname --vm
consistently reproduces.less /var/log/cloud-init.log
Traceback
should be above the fold in the logs.