canonical-ubuntu-qa team mailing list archive

[Paride Legovini <2078981@xxxxxxxxxxxxxxxxxx>]

Hi Dan, where/how did you hit this issue exactly? Is this about the
autopkgtest.ubuntu.com or running autopkgtest locally? In the latter
case, which version, and which virt-server are you using?

Newer versions of autopkgtest should not use a tmpfs for /tmp:

autopkgtest (5.36) unstable; urgency=medium

  [...]
  * setup-testbed: prevent /tmp from getting a tmpfs mount (LP: #2069834)

so we need more info to triage this bug.

Thanks!

** Changed in: autopkgtest (Ubuntu)
       Status: New => Incomplete

-- 
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