On 2024-02-16 I created a 29-days old test file in one of the cloud workers:
$ touch -d "29 days ago" /tmp/I-am-an-old-file The machine has this tmpfile conf: e /tmp 1777 root root 30d however the 3 days later the file did not get deleted. Checking timestamps I found: buntu@juju-7f2275-prod-proposed-migration-environment-2:~$ stat /tmp/I-am-an-old-file File: /tmp/I-am-an-old-file Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fc11h/64529d Inode: 94 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2024-01-18 16:55:36.354981825 +0000 Modify: 2024-01-18 16:55:36.354981825 +0000 Change: 2024-02-16 16:55:36.350943134 +0000 so something updated the atime of that file, and as a consequence it didn't get deleted. This is consistent with what Steve mentioned in comment 8 of LP: #2019026. To make this change useful we have to figure out what is touching files. -- https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/460680 Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:cloud-worker-tmp-cleanup into autopkgtest-cloud:master. -- 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
