0s autopkgtest [15:58:56]: starting date and time: 2025-10-21 15:58:56+0000 0s autopkgtest [15:58:56]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [15:58:56]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.itfe40df/out --timeout-copy=6000 -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:frr --apt-upgrade frr --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=frr/8.4.4-1.1ubuntu6.4 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor builder-cpu2-ram4-disk20 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-3.secgroup --name adt-noble-i386-frr-20251021-155856-juju-7f2275-prod-proposed-migration-environment-15-d360abd1-dd50-41cc-a198-7a33729aa82c --image adt/ubuntu-noble-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-noble-i386-frr-20251021-155856-juju-7f2275-prod-proposed-migration-environment-15-d360abd1-dd50-41cc-a198-7a33729aa82c from image adt/ubuntu-noble-amd64-server-20251021.img (UUID 791be440-7139-41d5-9055-91a5fd6193e7)... 63s autopkgtest [15:59:59]: testbed dpkg architecture: amd64 63s autopkgtest [15:59:59]: testbed apt version: 2.8.3 64s autopkgtest [16:00:00]: @@@@@@@@@@@@@@@@@@@@ test bed setup 64s autopkgtest [16:00:00]: testbed release detected to be: None 65s autopkgtest [16:00:01]: updating testbed package index (apt update) 65s Get:1 http://ftpmaster.internal/ubuntu noble-proposed InRelease [265 kB] 66s Hit:2 http://ftpmaster.internal/ubuntu noble InRelease 66s Hit:3 http://ftpmaster.internal/ubuntu noble-updates InRelease 66s Hit:4 http://ftpmaster.internal/ubuntu noble-security InRelease 66s Get:5 http://ftpmaster.internal/ubuntu noble-proposed/universe Sources [38.5 kB] 66s Get:6 http://ftpmaster.internal/ubuntu noble-proposed/main Sources [76.6 kB] 67s Get:7 http://ftpmaster.internal/ubuntu noble-proposed/multiverse Sources [9140 B] 67s Get:8 http://ftpmaster.internal/ubuntu noble-proposed/restricted Sources [44.0 kB] 67s Get:9 http://ftpmaster.internal/ubuntu noble-proposed/main i386 Packages [69.2 kB] 67s Get:10 http://ftpmaster.internal/ubuntu noble-proposed/main amd64 Packages [426 kB] 67s Get:11 http://ftpmaster.internal/ubuntu noble-proposed/main amd64 c-n-f Metadata [1692 B] 67s Get:12 http://ftpmaster.internal/ubuntu noble-proposed/restricted i386 Packages [21.0 kB] 67s Get:13 http://ftpmaster.internal/ubuntu noble-proposed/restricted amd64 Packages [934 kB] 68s Get:14 http://ftpmaster.internal/ubuntu noble-proposed/restricted amd64 c-n-f Metadata [448 B] 68s Get:15 http://ftpmaster.internal/ubuntu noble-proposed/universe i386 Packages [45.8 kB] 68s Get:16 http://ftpmaster.internal/ubuntu noble-proposed/universe amd64 Packages [87.5 kB] 69s Get:17 http://ftpmaster.internal/ubuntu noble-proposed/universe amd64 c-n-f Metadata [1940 B] 69s Get:18 http://ftpmaster.internal/ubuntu noble-proposed/multiverse i386 Packages [752 B] 69s Get:19 http://ftpmaster.internal/ubuntu noble-proposed/multiverse amd64 Packages [5280 B] 69s Get:20 http://ftpmaster.internal/ubuntu noble-proposed/multiverse amd64 c-n-f Metadata [284 B] 70s Fetched 2028 kB in 3s (612 kB/s) 72s Reading package lists... 72s Hit:1 http://ftpmaster.internal/ubuntu noble-proposed InRelease 72s Hit:2 http://ftpmaster.internal/ubuntu noble InRelease 73s Hit:3 http://ftpmaster.internal/ubuntu noble-updates InRelease 73s Hit:4 http://ftpmaster.internal/ubuntu noble-security InRelease 75s Reading package lists... 75s Reading package lists... 75s Building dependency tree... 75s Reading state information... 76s Calculating upgrade... 76s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 76s autopkgtest [16:00:12]: upgrading testbed (apt dist-upgrade and autopurge) 77s Reading package lists... 77s Building dependency tree... 77s Reading state information... 78s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 78s Starting 2 pkgProblemResolver with broken count: 0 78s Done 79s Entering ResolveByKeep 79s 79s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 80s Reading package lists... 80s Building dependency tree... 80s Reading state information... 81s Starting pkgProblemResolver with broken count: 0 81s Starting 2 pkgProblemResolver with broken count: 0 81s Done 81s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 84s autopkgtest [16:00:20]: testbed running kernel: Linux 6.8.0-86-generic #87-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 18:03:36 UTC 2025 84s autopkgtest [16:00:20]: @@@@@@@@@@@@@@@@@@@@ apt-source frr 91s Get:1 http://ftpmaster.internal/ubuntu noble-proposed/main frr 8.4.4-1.1ubuntu6.4 (dsc) [2823 B] 91s Get:2 http://ftpmaster.internal/ubuntu noble-proposed/main frr 8.4.4-1.1ubuntu6.4 (tar) [7302 kB] 91s Get:3 http://ftpmaster.internal/ubuntu noble-proposed/main frr 8.4.4-1.1ubuntu6.4 (diff) [48.1 kB] 91s gpgv: Signature made Mon Oct 20 15:24:17 2025 UTC 91s gpgv: using RSA key 728EC353C51F5E144ED2808133876F7B2848893B 91s gpgv: Can't check signature: No public key 91s dpkg-source: warning: cannot verify inline signature for ./frr_8.4.4-1.1ubuntu6.4.dsc: no acceptable signature found 92s autopkgtest [16:00:28]: testing package frr version 8.4.4-1.1ubuntu6.4 94s autopkgtest [16:00:30]: build not needed 122s autopkgtest [16:00:58]: test zebra-lo: preparing testbed 122s Reading package lists... 123s Building dependency tree... 123s Reading state information... 123s Starting pkgProblemResolver with broken count: 1 123s Starting 2 pkgProblemResolver with broken count: 1 123s Investigating (0) satisfy:command-line:amd64 < none -> 1 @un puN Ib > 123s Broken satisfy:command-line:amd64 Depends on frr:i386:any < none @un H > 123s Done 123s Some packages could not be installed. This may mean that you have 123s requested an impossible situation or if you are using the unstable 123s distribution that some required packages have not yet been created 123s or been moved out of Incoming. 123s The following information may help to resolve the situation: 123s 123s The following packages have unmet dependencies: 123s satisfy:command-line : Depends: frr:i386 but it is not installable 123s E: Unable to correct problems, you have held broken packages. 123s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from noble-proposed 124s Reading package lists... 124s Building dependency tree... 124s Reading state information... 125s Starting pkgProblemResolver with broken count: 1 125s Starting 2 pkgProblemResolver with broken count: 1 125s Investigating (0) satisfy:command-line:amd64 < none -> 1 @un puN Ib > 125s Broken satisfy:command-line:amd64 Depends on frr:i386:any < none @un H > 125s Done 125s Some packages could not be installed. This may mean that you have 125s requested an impossible situation or if you are using the unstable 125s distribution that some required packages have not yet been created 125s or been moved out of Incoming. 125s The following information may help to resolve the situation: 125s 125s The following packages have unmet dependencies: 125s satisfy:command-line : Depends: frr:i386 but it is not installable 125s E: Unable to correct problems, you have held broken packages. 125s autopkgtest [16:01:01]: test bgpd-snmp-rpki: preparing testbed 125s zebra-lo FAIL badpkg 125s blame: frr 125s 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. 126s Reading package lists... 126s Building dependency tree... 126s Reading state information... 126s Starting pkgProblemResolver with broken count: 1 127s Starting 2 pkgProblemResolver with broken count: 1 127s Investigating (0) satisfy:command-line:amd64 < none -> 1 @un puN Ib > 127s Broken satisfy:command-line:amd64 Depends on frr:i386:any < none @un H > 127s Broken satisfy:command-line:amd64 Depends on frr-rpki-rtrlib:i386:any < none @un H > 127s Broken satisfy:command-line:amd64 Depends on frr-snmp:i386:any < none @un H > 127s Done 127s Some packages could not be installed. This may mean that you have 127s requested an impossible situation or if you are using the unstable 127s distribution that some required packages have not yet been created 127s or been moved out of Incoming. 127s The following information may help to resolve the situation: 127s 127s The following packages have unmet dependencies: 127s satisfy:command-line : Depends: frr:i386 but it is not installable 127s Depends: frr-rpki-rtrlib:i386 but it is not installable 127s Depends: frr-snmp:i386 but it is not installable 127s E: Unable to correct problems, you have held broken packages. 127s autopkgtest [16:01:03]: test py-frr-reload: preparing testbed 127s bgpd-snmp-rpki FAIL badpkg 127s blame: frr 127s 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. 148s Creating nova instance adt-noble-i386-frr-20251021-155856-juju-7f2275-prod-proposed-migration-environment-15-d360abd1-dd50-41cc-a198-7a33729aa82c from image adt/ubuntu-noble-amd64-server-20251021.img (UUID 791be440-7139-41d5-9055-91a5fd6193e7)... 213s autopkgtest [16:02:29]: testbed dpkg architecture: amd64 213s autopkgtest [16:02:29]: testbed apt version: 2.8.3 214s autopkgtest [16:02:30]: @@@@@@@@@@@@@@@@@@@@ test bed setup 214s autopkgtest [16:02:30]: testbed release detected to be: noble 215s autopkgtest [16:02:31]: updating testbed package index (apt update) 215s Get:1 http://ftpmaster.internal/ubuntu noble-proposed InRelease [265 kB] 216s Hit:2 http://ftpmaster.internal/ubuntu noble InRelease 216s Hit:3 http://ftpmaster.internal/ubuntu noble-updates InRelease 216s Hit:4 http://ftpmaster.internal/ubuntu noble-security InRelease 216s Get:5 http://ftpmaster.internal/ubuntu noble-proposed/universe Sources [38.5 kB] 216s Get:6 http://ftpmaster.internal/ubuntu noble-proposed/multiverse Sources [9140 B] 216s Get:7 http://ftpmaster.internal/ubuntu noble-proposed/main Sources [76.6 kB] 216s Get:8 http://ftpmaster.internal/ubuntu noble-proposed/restricted Sources [44.0 kB] 216s Get:9 http://ftpmaster.internal/ubuntu noble-proposed/main i386 Packages [69.2 kB] 216s Get:10 http://ftpmaster.internal/ubuntu noble-proposed/main amd64 Packages [426 kB] 216s Get:11 http://ftpmaster.internal/ubuntu noble-proposed/main amd64 c-n-f Metadata [1692 B] 216s Get:12 http://ftpmaster.internal/ubuntu noble-proposed/restricted i386 Packages [21.0 kB] 216s Get:13 http://ftpmaster.internal/ubuntu noble-proposed/restricted amd64 Packages [934 kB] 216s Get:14 http://ftpmaster.internal/ubuntu noble-proposed/restricted amd64 c-n-f Metadata [448 B] 216s Get:15 http://ftpmaster.internal/ubuntu noble-proposed/universe i386 Packages [45.8 kB] 216s Get:16 http://ftpmaster.internal/ubuntu noble-proposed/universe amd64 Packages [87.5 kB] 216s Get:17 http://ftpmaster.internal/ubuntu noble-proposed/universe amd64 c-n-f Metadata [1940 B] 216s Get:18 http://ftpmaster.internal/ubuntu noble-proposed/multiverse i386 Packages [752 B] 216s Get:19 http://ftpmaster.internal/ubuntu noble-proposed/multiverse amd64 Packages [5280 B] 216s Get:20 http://ftpmaster.internal/ubuntu noble-proposed/multiverse amd64 c-n-f Metadata [284 B] 219s Fetched 2028 kB in 1s (1894 kB/s) 220s Reading package lists... 221s Hit:1 http://ftpmaster.internal/ubuntu noble-proposed InRelease 221s Hit:2 http://ftpmaster.internal/ubuntu noble InRelease 221s Hit:3 http://ftpmaster.internal/ubuntu noble-updates InRelease 221s Hit:4 http://ftpmaster.internal/ubuntu noble-security InRelease 222s Reading package lists... 223s Reading package lists... 223s Building dependency tree... 223s Reading state information... 223s Calculating upgrade... 224s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 224s autopkgtest [16:02:40]: upgrading testbed (apt dist-upgrade and autopurge) 224s Reading package lists... 224s Building dependency tree... 224s Reading state information... 225s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 225s Starting 2 pkgProblemResolver with broken count: 0 225s Done 227s Entering ResolveByKeep 227s 228s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 228s Reading package lists... 228s Building dependency tree... 228s Reading state information... 229s Starting pkgProblemResolver with broken count: 0 229s Starting 2 pkgProblemResolver with broken count: 0 229s Done 230s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 233s Reading package lists... 233s Building dependency tree... 233s Reading state information... 234s Starting pkgProblemResolver with broken count: 1 234s Starting 2 pkgProblemResolver with broken count: 1 234s Investigating (0) satisfy:command-line:amd64 < none -> 1 @un puN Ib > 234s Broken satisfy:command-line:amd64 Depends on frr:i386:any < none @un H > 234s Broken satisfy:command-line:amd64 Depends on frr-pythontools:amd64 < none | 8.4.4-1.1ubuntu6.4 @un uH > 234s Considering frr-pythontools:amd64 1 as a solution to satisfy:command-line:amd64 9998 234s Re-Instated libcares2:amd64 234s Re-Instated libyang2t64:amd64 234s Re-Instated frr:amd64 234s Re-Instated frr-pythontools:amd64 234s Done 234s Some packages could not be installed. This may mean that you have 234s requested an impossible situation or if you are using the unstable 234s distribution that some required packages have not yet been created 234s or been moved out of Incoming. 234s The following information may help to resolve the situation: 234s 234s The following packages have unmet dependencies: 234s satisfy:command-line : Depends: frr:i386 but it is not installable 234s E: Unable to correct problems, you have held broken packages. 234s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from noble-proposed 235s Reading package lists... 236s Building dependency tree... 236s Reading state information... 236s Starting pkgProblemResolver with broken count: 1 236s Starting 2 pkgProblemResolver with broken count: 1 236s Investigating (0) satisfy:command-line:amd64 < none -> 1 @un puN Ib > 236s Broken satisfy:command-line:amd64 Depends on frr:i386:any < none @un H > 236s Broken satisfy:command-line:amd64 Depends on frr-pythontools:amd64 < none | 8.4.4-1.1ubuntu6.4 @un uH > 236s Considering frr-pythontools:amd64 1 as a solution to satisfy:command-line:amd64 9998 236s Re-Instated libcares2:amd64 236s Re-Instated libyang2t64:amd64 236s Re-Instated frr:amd64 236s Re-Instated frr-pythontools:amd64 236s Done 236s Some packages could not be installed. This may mean that you have 236s requested an impossible situation or if you are using the unstable 236s distribution that some required packages have not yet been created 236s or been moved out of Incoming. 236s The following information may help to resolve the situation: 236s 236s The following packages have unmet dependencies: 237s satisfy:command-line : Depends: frr:i386 but it is not installable 237s E: Unable to correct problems, you have held broken packages. 237s autopkgtest [16:02:53]: @@@@@@@@@@@@@@@@@@@@ summary 237s zebra-lo FAIL badpkg 237s blame: frr 237s 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. 237s bgpd-snmp-rpki FAIL badpkg 237s blame: frr 237s 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. 237s py-frr-reload FAIL badpkg 237s blame: frr 237s 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. 237s py-frr-reload FAIL badpkg 237s blame: frr 237s 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.