canonical-ubuntu-qa team mailing list archive
-
canonical-ubuntu-qa team
-
Mailing list archive
-
Message #05541
[Bug 2078981] Re: nodev tmp - should autopkgtest ensure that AUTOPKGTEST_TMP is available for dev node creation?
Hi Dan,
I have failed to replicate this bug locally for several days now. In
addition, the livecd-rootfs tests are also green despite running on the
same autopkgtest build. There might have been a semi-related issue with
the lxc virt-server but that has a fix committed and will be released
with the next version. I am closing this bug for now as cannot
replicate.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
Matching subscriptions: ubuntu-qa-bugs
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:
Won't Fix
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
References