Package: autopkgtest Version: 5.13.1 Severity: normal User: de...@kali.org Usertags: origin-kali
The default hostname in VMs created by autopkgtest-build-qemu is `host`, but that is not resolvable within the VM; this leads to some autopkgtests failing on the qemu backend, while succeeding on an lxc one. blackbox is such an example, as on qemu it fails with: command3 FAIL stderr: hostname: No address associated with hostname The following crude workaround gets that same test further: autopkgtest --setup-commands-boot='sed -i -e "s/localhost/localhost host/" /etc/hosts' [...] To stay on the blackbox example, this will still fail later on, but only for reasons unrelated to the bug at hand: blackbox' third tests lacks "Restrictions: needs-root" and possibly some other dependencies. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/36 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) 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 1.8.4 ii libdpkg-perl 1.19.7 ii procps 2:3.3.16-4 ii python3 3.8.2-3 ii python3-debian 0.1.36 Versions of packages autopkgtest recommends: ii autodep8 0.22 Versions of packages autopkgtest suggests: ii lxc 1:3.1.0+really3.0.4-2 pn lxd <none> ii ovmf 0~20191122.bd85bf54-1 ii qemu-efi-aarch64 0~20191122.bd85bf54-1 ii qemu-efi-arm 0~20191122.bd85bf54-1 ii qemu-system 1:4.2-1 ii qemu-utils 1:4.2-7 ii schroot 1.6.10-9 ii vmdb2 0.13.2+git20191220-1 -- no debconf information
