0s autopkgtest [18:25:23]: starting date and time: 2025-11-17 18:25:23+0000 0s autopkgtest [18:25:23]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [18:25:23]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.idvsv8b9/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:ruby-mongo --apt-upgrade ruby-mongo --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=ruby-mongo/2.21.3-1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-ppc64el-6.secgroup --name adt-resolute-ppc64el-ruby-mongo-20251117-182523-juju-7f2275-prod-proposed-migration-environment-2-4d367292-9764-4333-8a40-d867a2062961 --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-ppc64el-ruby-mongo-20251117-182523-juju-7f2275-prod-proposed-migration-environment-2-4d367292-9764-4333-8a40-d867a2062961 from image adt/ubuntu-resolute-ppc64el-server-20251117.img (UUID c6f5b741-c77a-45db-84cb-f00b40e77676)... 56s autopkgtest [18:26:19]: testbed dpkg architecture: ppc64el 56s autopkgtest [18:26:19]: testbed apt version: 3.1.11 57s autopkgtest [18:26:20]: @@@@@@@@@@@@@@@@@@@@ test bed setup 57s autopkgtest [18:26:20]: testbed release detected to be: None 58s autopkgtest [18:26:21]: updating testbed package index (apt update) 58s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 58s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 59s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 59s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 59s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [779 kB] 59s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [73.2 kB] 59s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9852 B] 59s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 59s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [135 kB] 59s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted ppc64el Packages [940 B] 59s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [501 kB] 60s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [11.0 kB] 60s Fetched 1622 kB in 2s (1016 kB/s) 61s Reading package lists... 61s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 61s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 61s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 62s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 62s Reading package lists... 62s Reading package lists... 63s Building dependency tree... 63s Reading state information... 63s Calculating upgrade... 63s The following packages will be upgraded: 63s apt libapt-pkg7.0 libcrypt-dev libcrypt1 usbutils 63s 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 63s Need to get 3180 kB of archives. 63s After this operation, 118 kB of additional disk space will be used. 63s Get:1 http://ftpmaster.internal/ubuntu resolute/main ppc64el libcrypt-dev ppc64el 1:4.5.1-1 [162 kB] 63s Get:2 http://ftpmaster.internal/ubuntu resolute/main ppc64el libcrypt1 ppc64el 1:4.5.1-1 [125 kB] 63s Get:3 http://ftpmaster.internal/ubuntu resolute/main ppc64el libapt-pkg7.0 ppc64el 3.1.12 [1286 kB] 64s Get:4 http://ftpmaster.internal/ubuntu resolute/main ppc64el apt ppc64el 3.1.12 [1516 kB] 64s Get:5 http://ftpmaster.internal/ubuntu resolute/main ppc64el usbutils ppc64el 1:019-1 [91.5 kB] 65s dpkg-preconfigure: unable to re-open stdin: No such file or directory 65s Fetched 3180 kB in 2s (1950 kB/s) 65s (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 ... 81022 files and directories currently installed.) 65s Preparing to unpack .../libcrypt-dev_1%3a4.5.1-1_ppc64el.deb ... 65s Unpacking libcrypt-dev:ppc64el (1:4.5.1-1) over (1:4.4.38-1build1) ... 65s Preparing to unpack .../libcrypt1_1%3a4.5.1-1_ppc64el.deb ... 65s Unpacking libcrypt1:ppc64el (1:4.5.1-1) over (1:4.4.38-1build1) ... 65s Setting up libcrypt1:ppc64el (1:4.5.1-1) ... 65s (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 ... 81022 files and directories currently installed.) 65s Preparing to unpack .../libapt-pkg7.0_3.1.12_ppc64el.deb ... 65s Unpacking libapt-pkg7.0:ppc64el (3.1.12) over (3.1.11) ... 65s Preparing to unpack .../apt_3.1.12_ppc64el.deb ... 65s Unpacking apt (3.1.12) over (3.1.11) ... 65s Preparing to unpack .../usbutils_1%3a019-1_ppc64el.deb ... 65s Unpacking usbutils (1:019-1) over (1:018-2) ... 65s Setting up usbutils (1:019-1) ... 65s Setting up libcrypt-dev:ppc64el (1:4.5.1-1) ... 65s Setting up libapt-pkg7.0:ppc64el (3.1.12) ... 65s Setting up apt (3.1.12) ... 66s Processing triggers for man-db (2.13.1-1) ... 68s Processing triggers for libc-bin (2.42-2ubuntu2) ... 68s autopkgtest [18:26:31]: upgrading testbed (apt dist-upgrade and autopurge) 69s Reading package lists... 69s Building dependency tree... 69s Reading state information... 69s Calculating upgrade... 69s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 70s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s Solving dependencies... 70s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 70s autopkgtest [18:26:33]: rebooting testbed after setup commands that affected boot 96s autopkgtest [18:26:59]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:02:41 UTC 2025 99s autopkgtest [18:27:02]: @@@@@@@@@@@@@@@@@@@@ apt-source ruby-mongo 101s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/universe ruby-mongo 2.21.3-1 (dsc) [2104 B] 101s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/universe ruby-mongo 2.21.3-1 (tar) [1304 kB] 101s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/universe ruby-mongo 2.21.3-1 (diff) [2948 B] 101s gpgv: Signature made Mon Nov 10 18:35:00 2025 UTC 101s gpgv: using RSA key 5C7ABEA20F8630459CC8C8B5E27F2CF8458C2FA4 101s gpgv: Can't check signature: No public key 101s dpkg-source: warning: cannot verify inline signature for ./ruby-mongo_2.21.3-1.dsc: no acceptable signature found 101s autopkgtest [18:27:04]: testing package ruby-mongo version 2.21.3-1 102s autopkgtest [18:27:05]: build not needed 104s autopkgtest [18:27:07]: test ci: preparing testbed 104s Reading package lists... 105s Building dependency tree... 105s Reading state information... 105s Solving dependencies... 105s Some packages could not be installed. This may mean that you have 105s requested an impossible situation or if you are using the unstable 105s distribution that some required packages have not yet been created 105s or been moved out of Incoming. 105s The following information may help to resolve the situation: 105s 105s The following packages have unmet dependencies: 105s satisfy:command-line : Depends: ruby-mongo but it is not going to be installed 105s Depends: mongodb-server but it is not installable 105s Depends: ruby-rspec but it is not going to be installed 105s E: Unable to satisfy dependencies. Reached two conflicting decisions: 105s 1. satisfy:command-line:ppc64el=1 is selected for install 105s 2. satisfy:command-line:ppc64el Depends mongodb-server 105s but none of the choices are installable: 105s [no choices] 105s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 105s Reading package lists... 105s Building dependency tree... 105s Reading state information... 105s Solving dependencies... 105s Some packages could not be installed. This may mean that you have 105s requested an impossible situation or if you are using the unstable 105s distribution that some required packages have not yet been created 105s or been moved out of Incoming. 105s The following information may help to resolve the situation: 105s 105s The following packages have unmet dependencies: 105s satisfy:command-line : Depends: ruby-mongo but it is not going to be installed 105s Depends: mongodb-server but it is not installable 105s Depends: ruby-rspec but it is not going to be installed 105s E: Unable to satisfy dependencies. Reached two conflicting decisions: 105s 1. satisfy:command-line:ppc64el=1 is selected for install 105s 2. satisfy:command-line:ppc64el Depends mongodb-server 105s but none of the choices are installable: 105s [no choices] 105s autopkgtest [18:27:08]: @@@@@@@@@@@@@@@@@@@@ summary 105s ci FAIL badpkg 105s blame: ruby-mongo 105s 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. 105s ci FAIL badpkg 105s blame: ruby-mongo 105s 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.