Auto Package Testing

Bug #2069834
Comment #12

Comment 12 for bug 2069834

Revision history for this message

Ural Tunaboyu (uralt) wrote on 2024-07-25:

#12

Performing the verification on Noble.

First, we check if we can reproduce the problem.

$ apt policy autopkgtest
autopkgtest:
  Installed: 5.34ubuntu2
  Candidate: 5.34ubuntu2
  Version table:
     5.37ubuntu3~24.04.1 100
        100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
*** 5.34ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
        100 /var/lib/dpkg/status

After creating an Oracular image we start a sample test:
$ autopkgtest -BU --shell gzip -- qemu -c 1 --ram 1024 autopkgtest-oracular-amd64.img

Then connect to the running Oracular instance and 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~24.04.1
  Candidate: 5.37ubuntu3~24.04.1
  Version table:
*** 5.37ubuntu3~24.04.1 100
        100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     5.34ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages

We recreate the Oracular image and rerun the sample test:
$ autopkgtest -BU --shell gzip -- qemu -c 1 --ram 1024 autopkgtest-oracular-amd64.img

Then connect to the running instance and 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: 253,1 Inode: 66 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2024-07-25 10:11:45.596093680 -0700
Modify: 2024-07-25 10:11:45.596093680 -0700
Change: 2024-07-25 10:11:45.596093680 -0700
Birth: 2024-07-25 10:11:45.595093432 -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 Noble.

Performing the verification on Noble.

First, we check if we can reproduce the problem.

$ apt policy autopkgtest
autopkgtest:
  Installed: 5.34ubuntu2
  Candidate: 5.34ubuntu2
  Version table:
     5.37ubuntu3~24.04.1 100
        100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
 *** 5.34ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
        100 /var/lib/dpkg/status

After creating an Oracular image we start a sample test:
$ autopkgtest -BU --shell gzip -- qemu -c 1 --ram 1024 autopkgtest-oracular-amd64.img

So the bug is successfully replicated.
Now we verify the fix.

$ apt policy autopkgtest
autopkgtest:
  Installed: 5.37ubuntu3~24.04.1
  Candidate: 5.37ubuntu3~24.04.1
  Version table:
 *** 5.37ubuntu3~24.04.1 100
        100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     5.34ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages

We recreate the Oracular image and rerun the sample test:
$ autopkgtest -BU --shell gzip -- qemu -c 1 --ram 1024 autopkgtest-oracular-amd64.img

Then connect to the running instance and 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: 253,1	Inode: 66          Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-07-25 10:11:45.596093680 -0700
Modify: 2024-07-25 10:11:45.596093680 -0700
Change: 2024-07-25 10:11:45.596093680 -0700
 Birth: 2024-07-25 10:11:45.595093432 -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 Noble.