Hello, Aurelien Jarno [17/Jan 12:36pm GMT] wrote: > I haven't looked at all the details, but here are a few things from the logs. > The reboot of tag2upload-builder-01 was scheduled at 14:12:29. It indeed > caused > a podman container to be stopped: > > Jan 10 14:12:30 tag2upload-builder-01 podman[1185600]: 2026-01-10 > 14:12:30.010520162 +0000 UTC m=+0.066434410 container exec_died > 972fbcb54ed17aac8387c04726a3adf71c176230bb7f8f1cb8ef0a3bd987bfa8 > (image=localhost/autopkgtest/debian:trixie, name=vibrant_williams, > org.debian.autopkgtest.release=trixie, org.debian.autopkgtest.vendor=debian, > io.buildah.version=1.39.3, org.debian.autopkgtest.dpkg_architecture=amd64, > org.debian.autopkgtest.init=none) > Jan 10 14:12:30 tag2upload-builder-01 podman[1185514]: 2026-01-10 > 14:12:30.014747754 +0000 UTC m=+0.879053969 container exec_died > 972fbcb54ed17aac8387c04726a3adf71c176230bb7f8f1cb8ef0a3bd987bfa8 > (image=localhost/autopkgtest/debian:trixie, name=vibrant_williams, > org.debian.autopkgtest.init=none, org.debian.autopkgtest.release=trixie, > org.debian.autopkgtest.vendor=debian, io.buildah.version=1.39.3, > org.debian.autopkgtest.dpkg_architecture=amd64) > Jan 10 14:12:40 tag2upload-builder-01 podman[1185609]: 2026-01-10 > 14:12:40.086522873 +0000 UTC m=+10.057610423 container died > 972fbcb54ed17aac8387c04726a3adf71c176230bb7f8f1cb8ef0a3bd987bfa8 > (image=localhost/autopkgtest/debian:trixie, name=vibrant_williams, > org.debian.autopkgtest.init=none, org.debian.autopkgtest.release=trixie, > org.debian.autopkgtest.vendor=debian, io.buildah.version=1.39.3, > org.debian.autopkgtest.dpkg_architecture=amd64) > Jan 10 14:12:40 tag2upload-builder-01 podman[1185609]: 2026-01-10 > 14:12:40.161691438 +0000 UTC m=+10.132778988 container cleanup > 972fbcb54ed17aac8387c04726a3adf71c176230bb7f8f1cb8ef0a3bd987bfa8 > (image=localhost/autopkgtest/debian:trixie, name=vibrant_williams, > org.debian.autopkgtest.release=trixie, org.debian.autopkgtest.vendor=debian, > io.buildah.version=1.39.3, org.debian.autopkgtest.dpkg_architecture=amd64, > org.debian.autopkgtest.init=none) > Jan 10 14:12:40 tag2upload-builder-01 podman[1185628]: 2026-01-10 > 14:12:40.217482299 +0000 UTC m=+0.045068826 container remove > 972fbcb54ed17aac8387c04726a3adf71c176230bb7f8f1cb8ef0a3bd987bfa8 > (image=localhost/autopkgtest/debian:trixie, name=vibrant_williams, > org.debian.autopkgtest.vendor=debian, io.buildah.version=1.39.3, > org.debian.autopkgtest.dpkg_architecture=amd64, > org.debian.autopkgtest.init=none, org.debian.autopkgtest.release=trixie)
Thanks for taking a look. That timing fits with our observations. > Could you please confirm from your logs that the reboot lock was > indeed taken by your tag2upload job? It doesn't print anything if it successfully takes the lock, but it prints something and exits if it fails to take the lock (verified by our test suite), and the logs indicate it did not exit. So, yes, I can confirm that the job did indeed take the lock. -- Sean Whitton
