Created attachment 4831 [details] Boot log from qemu https://autobuilder.yoctoproject.org/typhoon/#/builders/102/builds/2123 qemumips ubuntu2004-ty-2 The testing shows no serial login and no ssh connection. Looking at the boot log I can't see dropbear having started anywhere so this could be a dropbear startup issue. Bootlog attached
Created attachment 4832 [details] Test image log
Dropbear definitely in the image: qemumips-poky-linux/core-image-sato/1.0-r0/rootfs$ find -name *dropbear* ./lib/systemd/system-preset/98-dropbear.preset ./lib/systemd/system/dropbearkey.service ./lib/systemd/system/dropbear.socket ./lib/systemd/system/dropbear@.service ./etc/pam.d/dropbear ./etc/default/dropbear ./etc/systemd/system/sockets.target.wants/dropbear.socket ./etc/dropbear ./etc/dropbear/dropbear_rsa_host_key ./usr/sbin/dropbearmulti ./usr/sbin/dropbearconvert ./usr/sbin/dropbearkey ./usr/sbin/dropbear builddir placed in $HOME/saved on the AB
intermittent issue ? https://autobuilder.yoctoproject.org/typhoon/#/builders/102/builds/2289/steps/13/logs/stdio debian9-ty-2 qemumips-alt
this could be the same issue, happen on arm dropbearkey.service loaded failed failed SSH Key Generation this happened some time ago. tumbleweed-ty-3 qemuarm-alt https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/3097/steps/12/logs/stdio and happened again recently debian11-ty-1 qemuarm-alt https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/3228/steps/13/logs/stdio
Hasn't happened for months.