0s autopkgtest [15:48:29]: starting date and time: 2025-01-16 15:48:29+0000 0s autopkgtest [15:48:29]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [15:48:29]: host juju-7f2275-prod-proposed-migration-environment-9; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.qatfsw6r/out --timeout-copy=6000 --setup-commands 'ln -s /dev/null /etc/systemd/system/bluetooth.service; printf "http_proxy=http://squid.internal:3128\nhttps_proxy=http://squid.internal:3128\nno_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com,radosgw.ps5.canonical.com\n" >> /etc/environment' --apt-pocket=proposed=src:python-oslo.cache --apt-upgrade nova --timeout-short=300 --timeout-copy=20000 --timeout-test=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=python-oslo.cache/3.9.0-0ubuntu1 -- lxd -r lxd-armhf-10.145.243.201 lxd-armhf-10.145.243.201:autopkgtest/ubuntu/plucky/armhf 21s autopkgtest [15:48:50]: testbed dpkg architecture: armhf 23s autopkgtest [15:48:52]: testbed apt version: 2.9.18 29s autopkgtest [15:48:58]: @@@@@@@@@@@@@@@@@@@@ test bed setup 31s autopkgtest [15:49:00]: testbed release detected to be: None 41s autopkgtest [15:49:10]: updating testbed package index (apt update) 43s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 43s Get:2 http://ftpmaster.internal/ubuntu plucky InRelease [213 kB] 43s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 44s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 44s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [166 kB] 44s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 44s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.7 kB] 44s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [910 kB] 44s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf Packages [260 kB] 44s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted armhf Packages [756 B] 44s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe armhf Packages [947 kB] 44s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse armhf Packages [3692 B] 44s Get:13 http://ftpmaster.internal/ubuntu plucky/universe Sources [20.9 MB] 44s Get:14 http://ftpmaster.internal/ubuntu plucky/universe armhf Packages [15.2 MB] 48s Fetched 38.6 MB in 5s (7762 kB/s) 49s Reading package lists... 55s autopkgtest [15:49:24]: upgrading testbed (apt dist-upgrade and autopurge) 57s Reading package lists... 58s Building dependency tree... 58s Reading state information... 59s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 59s Starting 2 pkgProblemResolver with broken count: 0 59s Done 60s Entering ResolveByKeep 61s 61s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 64s Reading package lists... 64s Building dependency tree... 64s Reading state information... 64s Starting pkgProblemResolver with broken count: 0 65s Starting 2 pkgProblemResolver with broken count: 0 65s Done 66s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 69s autopkgtest [15:49:38]: rebooting testbed after setup commands that affected boot 115s autopkgtest [15:50:24]: testbed running kernel: Linux 6.8.0-49-generic #49~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 6 18:12:14 UTC 2 142s autopkgtest [15:50:51]: @@@@@@@@@@@@@@@@@@@@ apt-source nova 290s Get:1 http://ftpmaster.internal/ubuntu plucky/main nova 3:30.0.0-0ubuntu1 (dsc) [6820 B] 290s Get:2 http://ftpmaster.internal/ubuntu plucky/main nova 3:30.0.0-0ubuntu1 (tar) [9518 kB] 290s Get:3 http://ftpmaster.internal/ubuntu plucky/main nova 3:30.0.0-0ubuntu1 (diff) [42.2 kB] 291s gpgv: Signature made Thu Oct 3 09:36:26 2024 UTC 291s gpgv: using RSA key AB23E9A98422889E08C3838CBFECAECBA0E7D8C3 291s gpgv: Can't check signature: No public key 291s dpkg-source: warning: cannot verify inline signature for ./nova_30.0.0-0ubuntu1.dsc: no acceptable signature found 292s autopkgtest [15:53:21]: testing package nova version 3:30.0.0-0ubuntu1 295s autopkgtest [15:53:24]: build not needed 300s autopkgtest [15:53:29]: test nova-compute-daemons: preparing testbed 302s Reading package lists... 303s Building dependency tree... 303s Reading state information... 303s Starting pkgProblemResolver with broken count: 1 303s Starting 2 pkgProblemResolver with broken count: 1 303s Investigating (0) python3-ovsdbapp:armhf < none -> 2.8.0-0ubuntu1 @un puN Ib > 303s Broken python3-ovsdbapp:armhf Depends on python3-openvswitch:armhf < none @un H > (>= 2.10.0) 303s Done 303s Some packages could not be installed. This may mean that you have 303s requested an impossible situation or if you are using the unstable 303s distribution that some required packages have not yet been created 303s or been moved out of Incoming. 303s The following information may help to resolve the situation: 303s 303s The following packages have unmet dependencies: 304s python3-ovsdbapp : Depends: python3-openvswitch (>= 2.10.0) but it is not installable 304s E: Unable to correct problems, you have held broken packages. 304s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 309s Reading package lists... 310s Building dependency tree... 310s Reading state information... 310s Starting pkgProblemResolver with broken count: 1 310s Starting 2 pkgProblemResolver with broken count: 1 310s Investigating (0) python3-ovsdbapp:armhf < none -> 2.8.0-0ubuntu1 @un puN Ib > 310s Broken python3-ovsdbapp:armhf Depends on python3-openvswitch:armhf < none @un H > (>= 2.10.0) 310s Done 310s Some packages could not be installed. This may mean that you have 310s requested an impossible situation or if you are using the unstable 310s distribution that some required packages have not yet been created 310s or been moved out of Incoming. 310s The following information may help to resolve the situation: 310s 310s The following packages have unmet dependencies: 311s python3-ovsdbapp : Depends: python3-openvswitch (>= 2.10.0) but it is not installable 311s E: Unable to correct problems, you have held broken packages. 311s autopkgtest [15:53:40]: test nova-daemons: preparing testbed 311s nova-compute-daemons FAIL badpkg 311s blame: nova 311s 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. 313s Reading package lists... 313s Building dependency tree... 313s Reading state information... 314s Starting pkgProblemResolver with broken count: 1 314s Starting 2 pkgProblemResolver with broken count: 1 314s Investigating (0) python3-ovsdbapp:armhf < none -> 2.8.0-0ubuntu1 @un puN Ib > 314s Broken python3-ovsdbapp:armhf Depends on python3-openvswitch:armhf < none @un H > (>= 2.10.0) 314s Done 314s Some packages could not be installed. This may mean that you have 314s requested an impossible situation or if you are using the unstable 314s distribution that some required packages have not yet been created 314s or been moved out of Incoming. 314s The following information may help to resolve the situation: 314s 314s The following packages have unmet dependencies: 314s python3-ovsdbapp : Depends: python3-openvswitch (>= 2.10.0) but it is not installable 314s E: Unable to correct problems, you have held broken packages. 314s nova-daemons FAIL badpkg 314s blame: nova 314s 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. 314s autopkgtest [15:53:43]: test nova-api: preparing testbed 317s Reading package lists... 318s Building dependency tree... 318s Reading state information... 318s Starting pkgProblemResolver with broken count: 1 318s Starting 2 pkgProblemResolver with broken count: 1 318s Investigating (0) python3-ovsdbapp:armhf < none -> 2.8.0-0ubuntu1 @un puN Ib > 318s Broken python3-ovsdbapp:armhf Depends on python3-openvswitch:armhf < none @un H > (>= 2.10.0) 318s Done 318s Some packages could not be installed. This may mean that you have 318s requested an impossible situation or if you are using the unstable 318s distribution that some required packages have not yet been created 318s or been moved out of Incoming. 318s The following information may help to resolve the situation: 318s 318s The following packages have unmet dependencies: 319s python3-ovsdbapp : Depends: python3-openvswitch (>= 2.10.0) but it is not installable 319s E: Unable to correct problems, you have held broken packages. 319s nova-api FAIL badpkg 319s blame: nova 319s 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. 319s autopkgtest [15:53:48]: @@@@@@@@@@@@@@@@@@@@ summary 319s nova-compute-daemons FAIL badpkg 319s blame: nova 319s 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. 319s nova-daemons FAIL badpkg 319s blame: nova 319s 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. 319s nova-api FAIL badpkg 319s blame: nova 319s 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.