0s autopkgtest [11:44:24]: starting date and time: 2025-12-03 11:44:24+0000 0s autopkgtest [11:44:24]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [11:44:24]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.ixjd5hdm/out --timeout-copy=6000 -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:python3-defaults --apt-upgrade ceph --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=python3-defaults/3.13.9-2 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-1.secgroup --name adt-resolute-i386-ceph-20251203-114424-juju-7f2275-prod-proposed-migration-environment-15-71316808-4d1b-4ef2-a6d8-ea698d5e2a40 --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-i386-ceph-20251203-114424-juju-7f2275-prod-proposed-migration-environment-15-71316808-4d1b-4ef2-a6d8-ea698d5e2a40 from image adt/ubuntu-resolute-amd64-server-20251203.img (UUID c6e78f39-c16c-48bb-9815-0096f6be052e)... 55s autopkgtest [11:45:19]: testbed dpkg architecture: amd64 56s autopkgtest [11:45:20]: testbed apt version: 3.1.12 56s autopkgtest [11:45:20]: @@@@@@@@@@@@@@@@@@@@ test bed setup 56s autopkgtest [11:45:20]: testbed release detected to be: None 57s autopkgtest [11:45:21]: updating testbed package index (apt update) 57s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 57s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 57s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 57s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 57s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [25.2 kB] 57s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [981 kB] 57s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [147 kB] 57s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [205 kB] 58s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [158 kB] 58s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [6168 B] 58s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [120 B] 58s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [742 kB] 58s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [343 kB] 58s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [23.3 kB] 58s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [5224 B] 58s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [11.5 kB] 58s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [828 B] 58s Fetched 2774 kB in 1s (3012 kB/s) 59s Reading package lists... 59s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 59s 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 60s Reading package lists... 60s Reading package lists... 60s Building dependency tree... 60s Reading state information... 60s Calculating upgrade... 60s The following packages will be upgraded: 60s libpython3-stdlib python3 python3-gdbm python3-minimal 60s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60s Need to get 72.9 kB of archives. 60s After this operation, 2048 B of additional disk space will be used. 60s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3-minimal amd64 3.13.9-2 [28.1 kB] 60s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3 amd64 3.13.9-2 [23.0 kB] 60s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 libpython3-stdlib amd64 3.13.9-2 [10.8 kB] 60s Get:4 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3-gdbm amd64 3.13.9-2 [11.0 kB] 61s dpkg-preconfigure: unable to re-open stdin: No such file or directory 61s Fetched 72.9 kB in 0s (0 B/s) 61s (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 ... 83538 files and directories currently installed.) 61s Preparing to unpack .../python3-minimal_3.13.9-2_amd64.deb ... 61s Unpacking python3-minimal (3.13.9-2) over (3.13.7-1) ... 61s Setting up python3-minimal (3.13.9-2) ... 61s (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 ... 83538 files and directories currently installed.) 61s Preparing to unpack .../python3_3.13.9-2_amd64.deb ... 61s running python pre-rtupdate hooks for python3.13... 61s Unpacking python3 (3.13.9-2) over (3.13.7-1) ... 61s Preparing to unpack .../libpython3-stdlib_3.13.9-2_amd64.deb ... 61s Unpacking libpython3-stdlib:amd64 (3.13.9-2) over (3.13.7-1) ... 61s Preparing to unpack .../python3-gdbm_3.13.9-2_amd64.deb ... 61s Unpacking python3-gdbm (3.13.9-2) over (3.13.9-1) ... 61s Setting up python3-gdbm (3.13.9-2) ... 61s Setting up libpython3-stdlib:amd64 (3.13.9-2) ... 61s Setting up python3 (3.13.9-2) ... 61s running python rtupdate hooks for python3.13... 61s running python post-rtupdate hooks for python3.13... 61s Processing triggers for man-db (2.13.1-1) ... 62s autopkgtest [11:45:26]: upgrading testbed (apt dist-upgrade and autopurge) 62s Reading package lists... 62s Building dependency tree... 62s Reading state information... 62s Calculating upgrade... 62s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62s Reading package lists... 62s Building dependency tree... 62s Reading state information... 62s Solving dependencies... 62s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 64s autopkgtest [11:45:28]: testbed running kernel: Linux 6.17.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 7 13:34:17 UTC 2025 64s autopkgtest [11:45:28]: @@@@@@@@@@@@@@@@@@@@ apt-source ceph 86s Get:1 http://ftpmaster.internal/ubuntu resolute/main ceph 19.2.3-0ubuntu2 (dsc) [7341 B] 86s Get:2 http://ftpmaster.internal/ubuntu resolute/main ceph 19.2.3-0ubuntu2 (tar) [152 MB] 86s Get:3 http://ftpmaster.internal/ubuntu resolute/main ceph 19.2.3-0ubuntu2 (diff) [141 kB] 86s gpgv: Signature made Thu Oct 23 12:05:15 2025 UTC 86s gpgv: using RSA key AEFA16D4EF326839D7A972E7BF0653AF824B8BF7 86s gpgv: issuer "rr@ubuntu.com" 86s gpgv: Can't check signature: No public key 86s dpkg-source: warning: cannot verify inline signature for ./ceph_19.2.3-0ubuntu2.dsc: no acceptable signature found 91s autopkgtest [11:45:55]: testing package ceph version 19.2.3-0ubuntu2 93s autopkgtest [11:45:57]: build not needed 142s autopkgtest [11:46:46]: test ceph-client: preparing testbed 142s Reading package lists... 142s Building dependency tree... 142s Reading state information... 142s Solving dependencies... 142s Some packages could not be installed. This may mean that you have 142s requested an impossible situation or if you are using the unstable 142s distribution that some required packages have not yet been created 142s or been moved out of Incoming. 142s The following information may help to resolve the situation: 142s 142s The following packages have unmet dependencies: 142s satisfy:command-line : Depends: ceph-common:i386 but it is not installable 142s Depends: librados-dev:i386 but it is not installable 142s Depends: librbd-dev:i386 but it is not installable 142s Depends: python3-rados:i386 but it is not installable 142s Depends: python3-rbd:i386 but it is not installable 142s Depends: build-essential:amd64 142s Depends: crossbuild-essential-i386:amd64 142s Depends: libc-dev:i386 142s Depends: libstdc++-dev:i386 142s E: Unable to satisfy dependencies. Reached two conflicting decisions: 142s 1. satisfy:command-line:amd64=1 is selected for install 142s 2. satisfy:command-line:amd64 Depends python3-rados:i386 142s but none of the choices are installable: 142s [no choices] 142s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 143s Reading package lists... 143s Building dependency tree... 143s Reading state information... 143s Solving dependencies... 143s Some packages could not be installed. This may mean that you have 143s requested an impossible situation or if you are using the unstable 143s distribution that some required packages have not yet been created 143s or been moved out of Incoming. 143s The following information may help to resolve the situation: 143s 143s The following packages have unmet dependencies: 143s satisfy:command-line : Depends: ceph-common:i386 but it is not installable 143s Depends: librados-dev:i386 but it is not installable 143s Depends: librbd-dev:i386 but it is not installable 143s Depends: python3-rados:i386 but it is not installable 143s Depends: python3-rbd:i386 but it is not installable 143s Depends: build-essential:amd64 143s Depends: crossbuild-essential-i386:amd64 143s Depends: libc-dev:i386 143s Depends: libstdc++-dev:i386 143s E: Unable to satisfy dependencies. Reached two conflicting decisions: 143s 1. satisfy:command-line:amd64=1 is selected for install 143s 2. satisfy:command-line:amd64 Depends librbd-dev:i386 143s but none of the choices are installable: 143s [no choices] 143s ceph-client FAIL badpkg 143s blame: ceph 143s 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. 143s autopkgtest [11:46:47]: test build-rados: preparing testbed 143s Reading package lists... 143s Building dependency tree... 143s Reading state information... 143s Solving dependencies... 143s Some packages could not be installed. This may mean that you have 143s requested an impossible situation or if you are using the unstable 143s distribution that some required packages have not yet been created 143s or been moved out of Incoming. 143s The following information may help to resolve the situation: 143s 143s The following packages have unmet dependencies: 143s satisfy:command-line : Depends: ceph-common:i386 but it is not installable 143s Depends: librados-dev:i386 but it is not installable 143s Depends: librbd-dev:i386 but it is not installable 143s Depends: python3-rados:i386 but it is not installable 143s Depends: python3-rbd:i386 but it is not installable 143s Depends: build-essential:amd64 143s Depends: crossbuild-essential-i386:amd64 143s Depends: libc-dev:i386 143s Depends: libstdc++-dev:i386 143s E: Unable to satisfy dependencies. Reached two conflicting decisions: 143s 1. satisfy:command-line:amd64=1 is selected for install 143s 2. satisfy:command-line:amd64 Depends librbd-dev:i386 143s but none of the choices are installable: 143s [no choices] 143s build-rados FAIL badpkg 143s blame: ceph 143s 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. 143s autopkgtest [11:46:47]: test build-rbd: preparing testbed 144s Reading package lists... 144s Building dependency tree... 144s Reading state information... 144s Solving dependencies... 144s Some packages could not be installed. This may mean that you have 144s requested an impossible situation or if you are using the unstable 144s distribution that some required packages have not yet been created 144s or been moved out of Incoming. 144s The following information may help to resolve the situation: 144s 144s The following packages have unmet dependencies: 144s satisfy:command-line : Depends: ceph-common:i386 but it is not installable 144s Depends: librados-dev:i386 but it is not installable 144s Depends: librbd-dev:i386 but it is not installable 144s Depends: python3-rados:i386 but it is not installable 144s Depends: python3-rbd:i386 but it is not installable 144s Depends: build-essential:amd64 144s Depends: crossbuild-essential-i386:amd64 144s Depends: libc-dev:i386 144s Depends: libstdc++-dev:i386 144s E: Unable to satisfy dependencies. Reached two conflicting decisions: 144s 1. satisfy:command-line:amd64=1 is selected for install 144s 2. satisfy:command-line:amd64 Depends librbd-dev:i386 144s but none of the choices are installable: 144s [no choices] 144s build-rbd FAIL badpkg 144s blame: ceph 144s 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. 144s autopkgtest [11:46:48]: test python-ceph: preparing testbed 144s Reading package lists... 144s Building dependency tree... 144s Reading state information... 144s Solving dependencies... 144s Some packages could not be installed. This may mean that you have 144s requested an impossible situation or if you are using the unstable 144s distribution that some required packages have not yet been created 144s or been moved out of Incoming. 144s The following information may help to resolve the situation: 144s 144s The following packages have unmet dependencies: 144s satisfy:command-line : Depends: ceph-common:i386 but it is not installable 144s Depends: librados-dev:i386 but it is not installable 144s Depends: librbd-dev:i386 but it is not installable 144s Depends: python3-rados:i386 but it is not installable 144s Depends: python3-rbd:i386 but it is not installable 144s Depends: build-essential:amd64 144s Depends: crossbuild-essential-i386:amd64 144s Depends: libc-dev:i386 144s Depends: libstdc++-dev:i386 144s E: Unable to satisfy dependencies. Reached two conflicting decisions: 144s 1. satisfy:command-line:amd64=1 is selected for install 144s 2. satisfy:command-line:amd64 Depends librbd-dev:i386 144s but none of the choices are installable: 144s [no choices] 144s python-ceph FAIL badpkg 144s blame: ceph 144s 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. 144s autopkgtest [11:46:48]: @@@@@@@@@@@@@@@@@@@@ summary 144s ceph-client FAIL badpkg 144s blame: ceph 144s 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. 144s build-rados FAIL badpkg 144s blame: ceph 144s 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. 144s build-rbd FAIL badpkg 144s blame: ceph 144s 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. 144s python-ceph FAIL badpkg 144s blame: ceph 144s 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.