Your message dated Thu, 14 Nov 2024 09:39:06 +0000 with message-id <zzxfoij4vkmio...@remnant.pseudorandom.co.uk> and subject line Re: Bug#1086179: mkdir: cannot create directory ‘/tmp/autopkgtest-lxc.xxx/downtmp’: No such file or directory has caused the Debian Bug report #1086179, regarding mkdir: cannot create directory ‘/tmp/autopkgtest-lxc.xxx/downtmp’: No such file or directory to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1086179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: autopkgtest Version: 5.41 Severity: serious -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I see autopkgtest failing to start with the following error: autopkgtest [13:53:25]: version 5.42 autopkgtest [13:53:25]: host <..>; command line: /usr/bin/autopkgtest --user debci --apt-upgrade -s --output-dir=<..> '<..>/<package>_<version>_amd64.changes' -- lxc --sudo autopkgtest-unstable-amd64 <VirtSubproc>: failure: (down) ['mkdir', '-m', '777', '/tmp/autopkgtest-lxc.u7ggq9ma/downtmp'] failed (exit status 1, stderr 'mkdir: cannot create directory ‘/tmp/autopkgtest-lxc.u7ggq9ma/downtmp’: No such file or directory\n') autopkgtest [13:53:44]: ERROR: testbed failure: unexpected eof from the testbed Interestingly, this happens for the autopkgtest-unstable-amd64 container, but not with the autopkgtest-jammy-amd64 container. All containers have been created some time ago. The error happens with version 5.41 as well. I cannot find version 5.40 to test. If I downgrade autopkgtest to version 5.39 in testing, everything is working. Regards, Daniel - -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.11.4-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages autopkgtest depends on: ii apt-utils 2.9.10 ii libdpkg-perl 1.22.11 ii mawk 1.3.4.20240905-1 ii procps 2:4.0.4-6 ii python3 3.12.6-1 ii python3-debian 0.1.49 ii python3-distro-info 1.12 ii retry 1.0.5-3 Versions of packages autopkgtest recommends: ii autodep8 0.28+nmu1 ii fakeroot 1.36-1 Versions of packages autopkgtest suggests: ii docker-cli 26.1.5+dfsg1-2+b2 ii docker.io 26.1.5+dfsg1-2+b2 pn fakemachine <none> ii genisoimage 9:1.1.11-3.5 pn incus <none> ii lxc 1:6.0.2-1 pn lxd <none> ii ovmf 2024.08-4 pn ovmf-ia32 <none> pn podman <none> ii qemu-efi-aarch64 2024.08-4 ii qemu-efi-arm 2024.08-4 pn qemu-efi-riscv64 <none> pn qemu-system <none> ii qemu-utils 1:9.1.1+ds-2 ii schroot 1.6.13-5 ii util-linux 2.40.2-9 ii vmdb2 0.40-2 ii zerofree 1.1.1-1+b1 - -- no debconf information -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmcfjOUACgkQS80FZ8KW 0F3UXw//V9YvM1VfKV/hMJuO5heoxh28R/MyjoBTWUFSHghRFzjdM8CV/wY/b9yL +pZbBhozwSfXClY1wy422MGAVBFEH1WUt+WHScLCkFyx1gqGcvkbjAw4H8+befzz FxU/m8qBYW83o9gd2zwYpo9FyxGXr7FXTHCgknzWu26yjLxpO6c1n0BpCHOFGhCa S0gdQ67enPofPlkY/vNGgmjbaqtpRp6FCJbC1YyfIZaiAwrUoe4CxoSbV1a8r5Xr eoCtcyMLMXMXqtIGzKcFffnyykigs4TOGp+NfC68rvTbLUMWrrPMIQGC5ai1bWsI YFB4eYICaS9K4lGJDpQi5twBOPzjm7KSFIRFJtLtsS1IueeR+TT0S7pRkEtqBu1K dvpthIQLJ40ieYGHZ2otjg8H61VXqyyIGruENfdejT48S023/ZwSOwZdDLRm+ulU cjYMRugW/3dBCidS3rKY05QBMAXbsL7ZvQcLk4jBbJPx6dySuA9GeBLVjxb906bw 2T5Ko5on777JkByaebIH/LxuKp7e4sJMuz3G7fR0dwh34w7KL9UNw1/rjYcuL9zj lNthoUyKhvZrZB1xv1qpYXSIybxl8u0oQ8v5rdT4r1G5nxeDKrLR64ppnHoy3gwt g0O0TQvzQFVCydRlu/hDU/VcQIayCZcTb/lGUzLxS8a/jKOHAkg= =L8GL -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---On Sun, 10 Nov 2024 at 20:09:20 +0100, Daniel Leidert wrote: ... > > On 28-10-2024 15:38, Paride Legovini wrote: > > > Can you please verify this by recreating the containers from > > > scratch with autopkgtest-build-lxc from autopkgtest 5.42? > > I don't see the issue with a container created from scratch. In that case, I think there is nothing more to be done about this: it's a bug in the version of autopkgtest-build-lxc that you used to create your older container (specifically, a bad interaction between newer versions of systemd, older versions of autopkgtest-build-lxc, and the assumption made by autopkgtest that it can bind-mount directories below /tmp), and it has been fixed in newer autopkgtest-build-lxc. smcv
--- End Message ---
