Hey Paride, I've seen it on autopkgtest.ubuntu.com - here is a sample failing log: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/arm64/l/livecd-rootfs/20240904_153439_e1e52@/log.gz
I have also seen it locally, but I can't reproduce that now. Presumably because I'm not using rebuilt images with the fix you list. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2078981 Title: nodev tmp - should autopkgtest ensure that AUTOPKGTEST_TMP is available for dev node creation? Status in autopkgtest package in Ubuntu: Incomplete Bug description: Related bugs: LP: #2075546, LP: #2078980 It appears that an implication of systemd tmp.mount is that /tmp may be mounted as nodev, as can be seen in some cases now when using the qemu backend for an Oracular image. autopkgtests running in an isolation-machine environment would reasonably conclude that they could create device nodes, certainly a requirement for livecd-rootfs and I expect others. AUTOPKGTEST_TMP today is of the form /tmp/autopkgtest.tA1oiD/autopkgtest_tmp in the current setup, so /tmp being nodev should mean that AUTOPKGTEST_TMP is as well. As an explicit interface, I suggest that AUTOPKGTEST_TMP should be located somewhere that dev nodes can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2078981/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
