Performing the verification on Jammy.
First, we check if we can reproduce the problem.
$ apt policy autopkgtest
autopkgtest:
Installed: 5.32ubuntu3~22.04.1
Candidate: 5.32ubuntu3~22.04.1
Version table:
5.37ubuntu3~22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages
*** 5.32ubuntu3~22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
100 /var/lib/dpkg/status
5.20 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
After creating an Oracular image we boot it and connect to it:
$ kvm -m 4096 -display none -boot c -net nic -net
user,hostfwd=tcp:127.0.0.1:10030-:22 -hda autopkgtest-oracular-amd64.img
Now we check:
$ mount -t tmpfs | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=1048576,inode64)
$ stat /etc/systemd/system/tmp.mount
stat: cannot statx '/etc/systemd/system/tmp.mount': No such file or directory
So the bug is successfully replicated.
Now we verify the fix.
$ apt policy autopkgtest
autopkgtest:
Installed: 5.37ubuntu3~22.04.1
Candidate: 5.37ubuntu3~22.04.1
Version table:
*** 5.37ubuntu3~22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages
100 /var/lib/dpkg/status
5.32ubuntu3~22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
5.20 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
We recreate the Oracular image and connect to it again:
$ kvm -m 4096 -display none -boot c -net nic -net
user,hostfwd=tcp:127.0.0.1:10030-:22 -hda autopkgtest-oracular-amd64.img
Now we check:
$ mount -t tmpfs | grep /tmp
$ stat /etc/systemd/system/tmp.mount
File: /etc/systemd/system/tmp.mount
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 8,1 Inode: 66 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2024-07-25 16:34:24.461607976 -0700
Modify: 2024-07-25 16:34:24.461607976 -0700
Change: 2024-07-25 16:34:24.461607976 -0700
Birth: 2024-07-25 16:34:24.460607752 -0700
As can be seen, systemd has been instructed to not make /tmp a tmpfs and
has done so without issue.
This concludes the verification for Jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069834
Title:
systemd defaulting to tmpfs for /tmp causes enospc errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2069834/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
