0s autopkgtest [21:19:27]: starting date and time: 2025-12-02 21:19:27+0000 0s autopkgtest [21:19:27]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [21:19:27]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.vpb4dnfy/out --timeout-copy=6000 -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:procps --apt-upgrade livecd-rootfs --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=procps/2:4.0.4-9ubuntu1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@sto01-5.secgroup --name adt-resolute-i386-livecd-rootfs-20251202-211927-juju-7f2275-prod-proposed-migration-environment-2-f3888ae9-4f6c-47c4-9bd2-4c7dc6e208c3 --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-i386-livecd-rootfs-20251202-211927-juju-7f2275-prod-proposed-migration-environment-2-f3888ae9-4f6c-47c4-9bd2-4c7dc6e208c3 from image adt/ubuntu-resolute-amd64-server-20251202.img (UUID 2f738dd5-7fa2-4ca0-90f0-baf94e87c733)... 45s autopkgtest [21:20:12]: testbed dpkg architecture: amd64 45s autopkgtest [21:20:12]: testbed apt version: 3.1.12 46s autopkgtest [21:20:13]: @@@@@@@@@@@@@@@@@@@@ test bed setup 46s autopkgtest [21:20:13]: testbed release detected to be: None 47s autopkgtest [21:20:14]: updating testbed package index (apt update) 47s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 47s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 47s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 47s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 47s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [20.5 kB] 47s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [829 kB] 48s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [132 kB] 48s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [122 kB] 48s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [97.0 kB] 48s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [5436 B] 48s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [120 B] 48s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [272 kB] 48s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [576 kB] 48s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [18.3 kB] 48s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3452 B] 48s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [8032 B] 48s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [616 B] 49s Fetched 2208 kB in 1s (2075 kB/s) 50s Reading package lists... 50s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 50s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 51s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 51s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 51s Reading package lists... 51s Reading package lists... 51s Building dependency tree... 51s Reading state information... 51s Calculating upgrade... 51s The following packages will be upgraded: 51s libproc2-0 procps python3-jmespath 51s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 51s Need to get 791 kB of archives. 51s After this operation, 32.8 kB disk space will be freed. 51s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 libproc2-0 amd64 2:4.0.4-9ubuntu1 [59.4 kB] 51s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 procps amd64 2:4.0.4-9ubuntu1 [710 kB] 52s Get:3 http://ftpmaster.internal/ubuntu resolute/main amd64 python3-jmespath all 1.0.1-1build1 [21.2 kB] 52s dpkg-preconfigure: unable to re-open stdin: No such file or directory 52s Fetched 791 kB in 0s (2783 kB/s) 52s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 123179 files and directories currently installed.) 52s Preparing to unpack .../libproc2-0_2%3a4.0.4-9ubuntu1_amd64.deb ... 52s Unpacking libproc2-0:amd64 (2:4.0.4-9ubuntu1) over (2:4.0.4-8ubuntu3) ... 52s Preparing to unpack .../procps_2%3a4.0.4-9ubuntu1_amd64.deb ... 52s Unpacking procps (2:4.0.4-9ubuntu1) over (2:4.0.4-8ubuntu3) ... 52s Preparing to unpack .../python3-jmespath_1.0.1-1build1_all.deb ... 52s Unpacking python3-jmespath (1.0.1-1build1) over (1.0.1-1) ... 52s Setting up python3-jmespath (1.0.1-1build1) ... 52s Setting up libproc2-0:amd64 (2:4.0.4-9ubuntu1) ... 52s Setting up procps (2:4.0.4-9ubuntu1) ... 53s Processing triggers for systemd (257.9-0ubuntu2) ... 53s Processing triggers for man-db (2.13.1-1) ... 53s Processing triggers for libc-bin (2.42-2ubuntu2) ... 54s autopkgtest [21:20:21]: upgrading testbed (apt dist-upgrade and autopurge) 54s Reading package lists... 54s Building dependency tree... 54s Reading state information... 54s Calculating upgrade... 54s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 54s Reading package lists... 54s Building dependency tree... 54s Reading state information... 54s Solving dependencies... 54s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 55s autopkgtest [21:20:22]: rebooting testbed after setup commands that affected boot 82s autopkgtest [21:20:49]: testbed running kernel: Linux 6.17.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 7 13:34:17 UTC 2025 84s autopkgtest [21:20:51]: @@@@@@@@@@@@@@@@@@@@ apt-source livecd-rootfs 85s Get:1 http://ftpmaster.internal/ubuntu resolute/main livecd-rootfs 26.04.9 (dsc) [1001 B] 85s Get:2 http://ftpmaster.internal/ubuntu resolute/main livecd-rootfs 26.04.9 (tar) [174 kB] 85s gpgv: Signature made Wed Nov 26 07:53:08 2025 UTC 85s gpgv: using DSA key DD00EF8F4D23C30D78EC990998B24A9CE4AC208E 85s gpgv: Can't check signature: No public key 85s dpkg-source: warning: cannot verify inline signature for ./livecd-rootfs_26.04.9.dsc: no acceptable signature found 85s autopkgtest [21:20:52]: testing package livecd-rootfs version 26.04.9 86s autopkgtest [21:20:53]: build not needed 86s autopkgtest [21:20:53]: test default-bootstraps: preparing testbed 86s Reading package lists... 86s Building dependency tree... 86s Reading state information... 86s Solving dependencies... 86s Some packages could not be installed. This may mean that you have 86s requested an impossible situation or if you are using the unstable 86s distribution that some required packages have not yet been created 86s or been moved out of Incoming. 86s The following information may help to resolve the situation: 86s 86s The following packages have unmet dependencies: 86s satisfy:command-line : Depends: livecd-rootfs:i386 86s E: Unable to satisfy dependencies. Reached two conflicting decisions: 86s 1. python3:i386 is selected for install because: 86s 1. satisfy:command-line:amd64=1 is selected for install 86s 2. satisfy:command-line:amd64 Depends livecd-rootfs:i386 86s 3. livecd-rootfs:i386 Depends python3:i386 86s 2. python3:i386 is available in versions 3.13.7-1, 3.13.7-2 86s but none of the choices are installable: 86s - python3:i386=3.13.7-1 is not selected for install because: 86s 1. shim-signed:amd64 is selected for install 86s 2. shim-signed:amd64 Depends grub2-common (>= 2.04-1ubuntu24) 86s 3. grub2-common:amd64 Depends python3 86s 4. python3:amd64 Conflicts python3:i386 86s [selected python3:amd64] 86s - python3:i386=3.13.7-2 is not selected for install 87s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 87s Reading package lists... 87s Building dependency tree... 87s Reading state information... 87s Solving dependencies... 87s Some packages could not be installed. This may mean that you have 87s requested an impossible situation or if you are using the unstable 87s distribution that some required packages have not yet been created 87s or been moved out of Incoming. 87s The following information may help to resolve the situation: 87s 87s The following packages have unmet dependencies: 87s satisfy:command-line : Depends: livecd-rootfs:i386 87s E: Unable to satisfy dependencies. Reached two conflicting decisions: 87s 1. python3:i386 is selected for install because: 87s 1. satisfy:command-line:amd64=1 is selected for install 87s 2. satisfy:command-line:amd64 Depends livecd-rootfs:i386 87s 3. livecd-rootfs:i386 Depends python3:i386 87s 2. python3:i386 is available in versions 3.13.7-2, 3.13.7-1 87s but none of the choices are installable: 87s - python3:i386=3.13.7-2 is not selected for install because: 87s 1. shim-signed:amd64 is selected for install 87s 2. shim-signed:amd64 Depends grub2-common (>= 2.04-1ubuntu24) 87s 3. grub2-common:amd64 Depends python3 87s 4. python3:amd64 Conflicts python3:i386 87s [selected python3:amd64] 87s - python3:i386=3.13.7-1 is not selected for install 87s default-bootstraps FAIL badpkg 87s blame: livecd-rootfs 87s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 87s autopkgtest [21:20:54]: test minimized: preparing testbed 87s Reading package lists... 87s Building dependency tree... 87s Reading state information... 87s Solving dependencies... 87s Some packages could not be installed. This may mean that you have 87s requested an impossible situation or if you are using the unstable 87s distribution that some required packages have not yet been created 87s or been moved out of Incoming. 87s The following information may help to resolve the situation: 87s 87s The following packages have unmet dependencies: 88s satisfy:command-line : Depends: livecd-rootfs:i386 88s E: Unable to satisfy dependencies. Reached two conflicting decisions: 88s 1. python3:i386 is selected for install because: 88s 1. satisfy:command-line:amd64=1 is selected for install 88s 2. satisfy:command-line:amd64 Depends livecd-rootfs:i386 88s 3. livecd-rootfs:i386 Depends python3:i386 88s 2. python3:i386 is available in versions 3.13.7-2, 3.13.7-1 88s but none of the choices are installable: 88s - python3:i386=3.13.7-2 is not selected for install because: 88s 1. shim-signed:amd64 is selected for install 88s 2. shim-signed:amd64 Depends grub2-common (>= 2.04-1ubuntu24) 88s 3. grub2-common:amd64 Depends python3 88s 4. python3:amd64 Conflicts python3:i386 88s [selected python3:amd64] 88s - python3:i386=3.13.7-1 is not selected for install 88s minimized FAIL badpkg 88s blame: livecd-rootfs 88s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 88s autopkgtest [21:20:55]: @@@@@@@@@@@@@@@@@@@@ summary 88s default-bootstraps FAIL badpkg 88s blame: livecd-rootfs 88s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 88s minimized FAIL badpkg 88s blame: livecd-rootfs 88s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.