0s autopkgtest [23:16:15]: starting date and time: 2026-04-07 23:16:15+0000 0s autopkgtest [23:16:15]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [23:16:15]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.87gd3q3l/out --timeout-copy=6000 --needs-internet=try --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:bind9 --apt-upgrade bind-dyndb-ldap --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=bind9/1:9.18.39-0ubuntu0.24.04.4 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-arm64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@sto01-arm64-21.secgroup --name adt-noble-arm64-bind-dyndb-ldap-20260407-231615-juju-7f2275-prod-proposed-migration-environment-20-b6d02197-e681-4c78-8be3-3d2ef325fcfa --image adt/ubuntu-noble-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-autopkgtest-workers-arm64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-noble-arm64-bind-dyndb-ldap-20260407-231615-juju-7f2275-prod-proposed-migration-environment-20-b6d02197-e681-4c78-8be3-3d2ef325fcfa from image adt/ubuntu-noble-arm64-server-20260407.img (UUID f0219259-cdee-4dee-b3a2-32f781d35bed)... 52s autopkgtest [23:17:07]: testbed dpkg architecture: arm64 52s autopkgtest [23:17:07]: testbed apt version: 2.8.3 53s autopkgtest [23:17:08]: @@@@@@@@@@@@@@@@@@@@ test bed setup 53s autopkgtest [23:17:08]: testbed release detected to be: None 53s autopkgtest [23:17:08]: updating testbed package index (apt update) 54s Get:1 http://ftpmaster.internal/ubuntu noble-proposed InRelease [265 kB] 54s Hit:2 http://ftpmaster.internal/ubuntu noble InRelease 54s Hit:3 http://ftpmaster.internal/ubuntu noble-updates InRelease 54s Hit:4 http://ftpmaster.internal/ubuntu noble-security InRelease 54s Get:5 http://ftpmaster.internal/ubuntu noble-proposed/universe Sources [35.8 kB] 54s Get:6 http://ftpmaster.internal/ubuntu noble-proposed/main Sources [66.3 kB] 54s Get:7 http://ftpmaster.internal/ubuntu noble-proposed/multiverse Sources [1984 B] 54s Get:8 http://ftpmaster.internal/ubuntu noble-proposed/restricted Sources [29.2 kB] 54s Get:9 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 Packages [575 kB] 54s Get:10 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 c-n-f Metadata [2840 B] 54s Get:11 http://ftpmaster.internal/ubuntu noble-proposed/restricted arm64 Packages [1626 kB] 54s Get:12 http://ftpmaster.internal/ubuntu noble-proposed/restricted arm64 c-n-f Metadata [116 B] 54s Get:13 http://ftpmaster.internal/ubuntu noble-proposed/universe arm64 Packages [170 kB] 54s Get:14 http://ftpmaster.internal/ubuntu noble-proposed/universe arm64 c-n-f Metadata [2464 B] 54s Get:15 http://ftpmaster.internal/ubuntu noble-proposed/multiverse arm64 Packages [15.1 kB] 54s Get:16 http://ftpmaster.internal/ubuntu noble-proposed/multiverse arm64 c-n-f Metadata [168 B] 57s Fetched 2790 kB in 1s (2756 kB/s) 58s Reading package lists... 59s Hit:1 http://ftpmaster.internal/ubuntu noble-proposed InRelease 59s Hit:2 http://ftpmaster.internal/ubuntu noble InRelease 59s Hit:3 http://ftpmaster.internal/ubuntu noble-updates InRelease 59s Hit:4 http://ftpmaster.internal/ubuntu noble-security InRelease 60s Reading package lists... 60s Reading package lists... 61s Building dependency tree... 61s Reading state information... 61s Calculating upgrade... 62s The following packages will be upgraded: 62s bind9-dnsutils bind9-host bind9-libs 62s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62s Need to get 1423 kB of archives. 62s After this operation, 0 B of additional disk space will be used. 62s Get:1 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 bind9-host arm64 1:9.18.39-0ubuntu0.24.04.4 [50.1 kB] 62s Get:2 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 bind9-dnsutils arm64 1:9.18.39-0ubuntu0.24.04.4 [156 kB] 62s Get:3 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 bind9-libs arm64 1:9.18.39-0ubuntu0.24.04.4 [1218 kB] 62s Fetched 1423 kB in 0s (4960 kB/s) 63s (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 ... 113795 files and directories currently installed.) 63s Preparing to unpack .../bind9-host_1%3a9.18.39-0ubuntu0.24.04.4_arm64.deb ... 63s Unpacking bind9-host (1:9.18.39-0ubuntu0.24.04.4) over (1:9.18.39-0ubuntu0.24.04.3) ... 63s Preparing to unpack .../bind9-dnsutils_1%3a9.18.39-0ubuntu0.24.04.4_arm64.deb ... 63s Unpacking bind9-dnsutils (1:9.18.39-0ubuntu0.24.04.4) over (1:9.18.39-0ubuntu0.24.04.3) ... 63s Preparing to unpack .../bind9-libs_1%3a9.18.39-0ubuntu0.24.04.4_arm64.deb ... 63s Unpacking bind9-libs:arm64 (1:9.18.39-0ubuntu0.24.04.4) over (1:9.18.39-0ubuntu0.24.04.3) ... 63s Setting up bind9-libs:arm64 (1:9.18.39-0ubuntu0.24.04.4) ... 63s Setting up bind9-host (1:9.18.39-0ubuntu0.24.04.4) ... 63s Setting up bind9-dnsutils (1:9.18.39-0ubuntu0.24.04.4) ... 63s Processing triggers for man-db (2.12.0-4build2) ... 63s Processing triggers for libc-bin (2.39-0ubuntu8.7) ... 64s autopkgtest [23:17:19]: upgrading testbed (apt dist-upgrade and autopurge) 64s Reading package lists... 64s Building dependency tree... 64s Reading state information... 65s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 65s Starting 2 pkgProblemResolver with broken count: 0 65s Done 66s Entering ResolveByKeep 66s 67s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 67s Reading package lists... 67s Building dependency tree... 67s Reading state information... 68s Starting pkgProblemResolver with broken count: 0 68s Starting 2 pkgProblemResolver with broken count: 0 68s Done 69s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 71s autopkgtest [23:17:26]: testbed running kernel: Linux 6.8.0-107-generic #107-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 13 19:42:33 UTC 2026 71s autopkgtest [23:17:26]: @@@@@@@@@@@@@@@@@@@@ apt-source bind-dyndb-ldap 73s Get:1 http://ftpmaster.internal/ubuntu noble-updates/universe bind-dyndb-ldap 11.10-6ubuntu11.24.04.5 (dsc) [2303 B] 73s Get:2 http://ftpmaster.internal/ubuntu noble-updates/universe bind-dyndb-ldap 11.10-6ubuntu11.24.04.5 (tar) [355 kB] 73s Get:3 http://ftpmaster.internal/ubuntu noble-updates/universe bind-dyndb-ldap 11.10-6ubuntu11.24.04.5 (diff) [13.8 kB] 73s gpgv: Signature made Tue Mar 24 20:45:54 2026 UTC 73s gpgv: using RSA key 50C4A0DDCF31E452CEB19B516569D855A744BE93 73s gpgv: Can't check signature: No public key 73s dpkg-source: warning: cannot verify inline signature for ./bind-dyndb-ldap_11.10-6ubuntu11.24.04.5.dsc: no acceptable signature found 73s autopkgtest [23:17:28]: testing package bind-dyndb-ldap version 11.10-6ubuntu11.24.04.5 73s autopkgtest [23:17:28]: build not needed 74s autopkgtest [23:17:29]: test dyndb-ldap: preparing testbed 74s Reading package lists... 75s Building dependency tree... 75s Reading state information... 75s Starting pkgProblemResolver with broken count: 1 75s Starting 2 pkgProblemResolver with broken count: 1 75s Investigating (0) bind9-dyndb-ldap:arm64 < none -> 11.10-6ubuntu11.24.04.5 @un puN Ib > 75s Broken bind9-dyndb-ldap:arm64 Depends on bind9-libs:arm64 < 1:9.18.39-0ubuntu0.24.04.4 @ii pK > (= 1:9.18.39-0ubuntu0.24.04.3) 75s Considering bind9-libs:arm64 15 as a solution to bind9-dyndb-ldap:arm64 0 75s Done 75s Some packages could not be installed. This may mean that you have 75s requested an impossible situation or if you are using the unstable 75s distribution that some required packages have not yet been created 75s or been moved out of Incoming. 75s The following information may help to resolve the situation: 75s 75s The following packages have unmet dependencies: 76s bind9-dyndb-ldap : Depends: bind9-libs (= 1:9.18.39-0ubuntu0.24.04.3) but 1:9.18.39-0ubuntu0.24.04.4 is to be installed 76s E: Unable to correct problems, you have held broken packages. 76s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from noble-proposed 76s Reading package lists... 76s Building dependency tree... 76s Reading state information... 77s Starting pkgProblemResolver with broken count: 1 77s Starting 2 pkgProblemResolver with broken count: 1 77s Investigating (0) bind9-dyndb-ldap:arm64 < none -> 11.10-6ubuntu11.24.04.5 @un puN Ib > 77s Broken bind9-dyndb-ldap:arm64 Depends on bind9-libs:arm64 < 1:9.18.39-0ubuntu0.24.04.4 @ii pK > (= 1:9.18.39-0ubuntu0.24.04.3) 77s Considering bind9-libs:arm64 15 as a solution to bind9-dyndb-ldap:arm64 0 77s Done 77s Some packages could not be installed. This may mean that you have 77s requested an impossible situation or if you are using the unstable 77s distribution that some required packages have not yet been created 77s or been moved out of Incoming. 77s The following information may help to resolve the situation: 77s 77s The following packages have unmet dependencies: 77s bind9-dyndb-ldap : Depends: bind9-libs (= 1:9.18.39-0ubuntu0.24.04.3) but 1:9.18.39-0ubuntu0.24.04.4 is to be installed 77s E: Unable to correct problems, you have held broken packages. 77s dyndb-ldap FAIL badpkg 77s blame: bind-dyndb-ldap 77s 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. 77s autopkgtest [23:17:32]: @@@@@@@@@@@@@@@@@@@@ summary 77s dyndb-ldap FAIL badpkg 77s blame: bind-dyndb-ldap 77s 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.