[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:fix-amqp-status-collector into autopkgtest-cloud:master
Tim Andersson has proposed merging
~andersson123/autopkgtest-cloud:fix-amqp-status-collector into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/463658
--
Your team Canonical's Ubuntu QA is requested to review the proposed merge of
~andersson123/autopkgtest-cloud:fix-amqp-status-collector into
autopkgtest-cloud:master.
diff --git a/charms/focal/autopkgtest-web/units/amqp-status-collector.service b/charms/focal/autopkgtest-web/units/amqp-status-collector.service
index d0f75de..bfb92ae 100644
--- a/charms/focal/autopkgtest-web/units/amqp-status-collector.service
+++ b/charms/focal/autopkgtest-web/units/amqp-status-collector.service
@@ -5,6 +5,7 @@ StartLimitBurst=60
[Service]
RuntimeDirectory=amqp-status-collector
+RuntimeDirectoryPreserve=yes
ExecStart=/home/ubuntu/webcontrol/amqp-status-collector
Restart=on-failure
RestartSec=1s
diff --git a/charms/focal/autopkgtest-web/webcontrol/amqp-status-collector b/charms/focal/autopkgtest-web/webcontrol/amqp-status-collector
index 1169f2e..68aac9c 100755
--- a/charms/focal/autopkgtest-web/webcontrol/amqp-status-collector
+++ b/charms/focal/autopkgtest-web/webcontrol/amqp-status-collector
@@ -6,6 +6,7 @@ import json
import logging
import os
import socket
+import sys
import time
import urllib.parse
@@ -116,4 +117,11 @@ status_ch.queue_bind(queue_name, exchange_name, queue_name)
logging.info("Listening to requests on %s" % queue_name)
status_ch.basic_consume("", callback=process_message, no_ack=True)
while status_ch.callbacks:
-status_ch.wait()
+try:
+status_ch.wait()
+except OSError as e:
+if "Transport endpoint is not connected" in str(e):
+logging.error(f"RabbitMQ is unresponsive: {str(e)}")
+else:
+logging.error(f"RabbitMQ callback failed with: {str(e)}")
+sys.exit(1)
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
Re: [Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:swift-cleanup into autopkgtest-cloud:master
from skia: from a very quick look, besides some function/variable naming, I'd say this is mostly OK. Maybe adding a "comment" key to the testinfo.json content, stating that this was touched by this script, with a date, would be good, for tracability. But, I think with the urgent matter of burning the queues before Friday to get images to build, we should wait before putting any more stress on swift. -- https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/463593 Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:swift-cleanup into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
Re: [Canonical-ubuntu-qa] [Merge] autopkgtest-cloud:no-raspi-kernel into autopkgtest-cloud:master
After further discussions we really shouldn't be running the linux-raspi kernel on arm64 so yes this is ready to merge. -- https://code.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/463642 Your team Canonical's Ubuntu QA is requested to review the proposed merge of autopkgtest-cloud:no-raspi-kernel into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic
** Changed in: autopkgtest (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2051939 Title: [SRU exception] backport 5.32 to Jammy and Mantic Status in autopkgtest package in Ubuntu: Fix Released Status in autopkgtest source package in Focal: Won't Fix Status in autopkgtest source package in Jammy: Fix Released Status in autopkgtest source package in Mantic: Fix Released Bug description: [Impact] This release contains both bug fixes and new features and we would like to make sure all of our developers have access to these improvements. It's a version bump from 5.28 to 5.32, so that's a big upstream upgrade with lots of improvements, but here are the most notable ones for developers: * Overall improved riscv64 support - QEMU fixes - Better timeouts by default * Add --cpus to buildvm-ubuntu-cloud tool: this improves speed when building images * Bump default QEMU ram size to 2048 (Debian #1059840), making a lot of tests work better by default See the changelog entry below for a full list of changes and bugs. [Test Plan] autopkgtest contains a test suite that is run using the SRU package for each release. This test suite's results are available here: Jammy (https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest-jammy/) Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest-jammy/jammy/amd64/a/autopkgtest/20240206_130746_30768@/log.gz As expected, the tests failed, but they've been forever failing on this release (see https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/autopkgtest/20240202_151346_e0140@/log.gz for example). However, with the current ongoing effort to fix them, we see an improvement with the `schroot` test being now PASS, and only `unshare` being FAIL. Most of the rest is now marked as SKIPPED instead of uncontroled FAIL, which also helps in the road to a green status. Mantic (https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-hyask-autopkgtest-mantic/) Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-hyask-autopkgtest-mantic/mantic/amd64/a/autopkgtest/20240206_155746_00441@/log.gz Unexpectedly, the tests are green on this release, which is a big improvement compared to the previous version (https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/a/autopkgtest/20240202_225722_a9ed0@/log.gz). As for Jammy, not everything is PASS, but the failures are under enough control to be marked as SKIP when needed. Additionally, the following PPAs should be tested manually at least under normal development conditions to ensure users will only be impacted by corner-case issues, should they arise: https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest-mantic/ https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest-jammy/ Please take a particular attention to test the cross-arch feature, as there is no automated tests for this. Here is the documentation on this feature: https://wiki.ubuntu.com/ProposedMigration#How_to_run_cross-architecture_autopkgtest_locally_using_QEMU Be knowledgeable that the `mawk` is particularly well suited for these kind of tests. [Where problems could occur] Given the size of the changelog, there may be corner-cases that aren't covered by the automated testsuite. Also, with the differences in Python version, some library interfaces could have changed in untested code, leading to crashes. Given that this tool is mainly used by developers, users are likely to find workarounds or report bugs when they find them. [Changelog] autopkgtest (5.32ubuntu2) noble; urgency=medium * Fix traceback in cross-arch testing (LP: #2051593) * Update cross-arch patchset from latest snapshot -- Paride Legovini Mon, 29 Jan 2024 22:46:58 +0100 autopkgtest (5.32ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2049737) Remaining changes: - Add support for cross-architecture testing. -- Paride Legovini Tue, 23 Jan 2024 12:00:37 +0100 autopkgtest (5.32) unstable; urgency=medium [ Florent 'Skia' Jacquet ] * d/t/schroot: better use of existing variables * d/t/schroot: allow running behind a proxy [ Simon McVittie ] * testarchive: Fix a pycodestyle warning * Standards-Version: 4.6.2 (no changes required) * qemu: Use 4M OVMF images if available [ Stefano Rivera ] * Testbed: Kill with SIGKILL if SIGTERM doesn't do the job in 10 seconds (Closes: #1059444) [ Paul Gevers ] * tests: increase sleep in test_timeout() for lxd test (Closes: #1020634) * autopkgtest-virt-qemu: raise time for command prompt return * virt-qemu: add context to several timeout errors [ Michael Biebl ] * Bump default ram-
[Canonical-ubuntu-qa] [Bug 2060187] Re: autopkgtest-build-qemu fails to build Ubuntu images
** Description changed: Normally autopkgtest-buildvm-ubuntu-cloud is a better tool to build Ubuntu images to be used with autopkgtest-virt-qemu, however we should also be able to use autopkgtest-build-qemu, which builds an image from scratch using debootstrap. This currently fails: - When building >= Focal images, autopkgtest-virt-qemu fails as it tries to install ifupdown on the testbed, which is not available in main (the only enabled component during debootstrap). We should stop installing - ifupdown in >= Focal or maybe >= Bionic. - - - When building Noble images, looks like debootstrap fails to install - coreutils, so the system is unusable. Maybe related to deb822 sources? - To be fixed somewhere else + ifupdown in >= Focal or more probably >= Bionic (when netplan has been + made the default). - Issues with setup-testbed installing rng-tools have been reported [1]. + Note: at the moment autopkgtest-build-qemu is also failing to build + noble images because the release pocket is currently missing binaries. + [1] https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/310 -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2060187 Title: autopkgtest-build-qemu fails to build Ubuntu images Status in autopkgtest package in Ubuntu: New Bug description: Normally autopkgtest-buildvm-ubuntu-cloud is a better tool to build Ubuntu images to be used with autopkgtest-virt-qemu, however we should also be able to use autopkgtest-build-qemu, which builds an image from scratch using debootstrap. This currently fails: - When building >= Focal images, autopkgtest-virt-qemu fails as it tries to install ifupdown on the testbed, which is not available in main (the only enabled component during debootstrap). We should stop installing ifupdown in >= Focal or more probably >= Bionic (when netplan has been made the default). - Issues with setup-testbed installing rng-tools have been reported [1]. Note: at the moment autopkgtest-build-qemu is also failing to build noble images because the release pocket is currently missing binaries. [1] https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2060187/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
This also happens with linux-aws-6.5 on jammy amd64. Sorry for the bad formatting: 767s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 768s autopkgtest [15:06:12]: rebooting testbed after setup commands that affected boot 784s autopkgtest [15:06:28]: testbed running kernel: Linux 5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024 785s autopkgtest [15:06:29]: apt-source linux-aws-6.5 786s blame: linux-aws-6.5 786s badpkg: rules extract failed with exit code 1 786s autopkgtest [15:06:30]: ERROR: erroneous package: rules extract failed with exit code 1 796s Creating nova instance adt-jammy-amd64-linux-aws-6.5-20240404-145324-juju-7f2275-prod-proposed-migration-environment-2-e4e1e79e-1749-4ae4-8386-7f19e3be6982 from image adt/ubuntu-jammy-amd64-server-20240404.img (UUID dc235da2-b119-4ee4-b09e-7c7ec6013d48) -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in Auto Package Testing: New Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2060117] Re: Merge autopkgtest 5.34 from Debian unstable
** Changed in: autopkgtest (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2060117 Title: Merge autopkgtest 5.34 from Debian unstable Status in autopkgtest package in Ubuntu: Fix Committed Bug description: Most notably autopkgtest 5.34 includes support for deb822 sources. Tracking bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2060117/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2060148] Re: White window when running "Install Ubuntu MATE 24.04 LTS" on Mar 28 test iso
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2060148 ** Tags added: iso-testing -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Ubuntu Manual Tests. https://bugs.launchpad.net/bugs/2060148 Title: White window when running "Install Ubuntu MATE 24.04 LTS" on Mar 28 test iso Status in Ubuntu Manual Tests: New Bug description: On the March 28 daily iso of Ubuntu MATE 24.04, when I run the installer I get a white window on the screen and the installer never starts. It worked for me on a previous build, not sure of its date. This is on a VirtualBox vm with 2gb memory and 15gb storage, which also worked previously. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/2060148/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2060213] Re: "apt failed to download packages, retrying in 10s..." results in " Unable to acquire the dpkg frontend lock"
This is also one case where we have the auto fallback to all-proposed: 869s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from noble-proposed which I'm not sure is desirable. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2060213 Title: "apt failed to download packages, retrying in 10s..." results in " Unable to acquire the dpkg frontend lock" Status in Auto Package Testing: New Bug description: logfile: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/armhf/b/balsa/20240404_081820_ad372@/log.gz pertinent log messages: ``` 883s Get:204 http://ftpmaster.internal/ubuntu noble-proposed/universe armhf xvfb armhf 2:21.1.11-2ubuntu2 [738 kB] 935s autopkgtest: WARNING: apt failed to download packages, retrying in 10s... 954s E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 763 (apt-get) 954s E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? 955s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 957s Reading package lists... 958s Building dependency tree... ``` It perhaps looks like in a setup script, whilst sleeping before a retry, another process starts an apt-get command which causes the script to fail after the sleep. Or something along those lines. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2060213/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2060187] [NEW] autopkgtest-build-qemu fails to build Ubuntu images
Public bug reported: Normally autopkgtest-buildvm-ubuntu-cloud is a better tool to build Ubuntu images to be used with autopkgtest-virt-qemu, however we should also be able to use autopkgtest-build-qemu, which builds an image from scratch using debootstrap. This currently fails: - When building >= Focal images, autopkgtest-virt-qemu fails as it tries to install ifupdown on the testbed, which is not available in main (the only enabled component during debootstrap). We should stop installing ifupdown in >= Focal or maybe >= Bionic. - When building Noble images, looks like debootstrap fails to install coreutils, so the system is unusable. Maybe related to deb822 sources? To be fixed somewhere else - Issues with setup-testbed installing rng-tools have been reported [1]. [1] https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/310 ** Affects: autopkgtest (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2060187 Title: autopkgtest-build-qemu fails to build Ubuntu images Status in autopkgtest package in Ubuntu: New Bug description: Normally autopkgtest-buildvm-ubuntu-cloud is a better tool to build Ubuntu images to be used with autopkgtest-virt-qemu, however we should also be able to use autopkgtest-build-qemu, which builds an image from scratch using debootstrap. This currently fails: - When building >= Focal images, autopkgtest-virt-qemu fails as it tries to install ifupdown on the testbed, which is not available in main (the only enabled component during debootstrap). We should stop installing ifupdown in >= Focal or maybe >= Bionic. - When building Noble images, looks like debootstrap fails to install coreutils, so the system is unusable. Maybe related to deb822 sources? To be fixed somewhere else - Issues with setup-testbed installing rng-tools have been reported [1]. [1] https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2060187/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2057734] Re: proc_sched_rt01 from ubuntu_ltp failed
Seen on focal:linux-oracle-5.15.0-1055.61~20.04.1 -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2057734 Title: proc_sched_rt01 from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Bug description: This is a new test case, issue found on M/J/F/B when testing LTP update 20240312 Test log: INFO: Test start time: Tue Mar 12 11:52:21 UTC 2024 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 163430 -n 163430 -f /tmp/ltp-X3Nz2HWCQe/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_kconfig.c:87: TINFO: Parsing kernel config '/lib/modules/6.5.0-27-generic/build/.config' tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568 tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s proc_sched_rt01.c:45: TFAIL: Expect: timeslice_ms > 0 after reset to default proc_sched_rt01.c:51: TPASS: echo 0 > /proc/sys/kernel/sched_rt_period_us : EINVAL (22) proc_sched_rt01.c:53: TFAIL: echo -1 > /proc/sys/kernel/sched_rt_period_us invalid retval 2: SUCCESS (0) proc_sched_rt01.c:59: TPASS: echo -2 > /proc/sys/kernel/sched_rt_runtime_us : EINVAL (22) proc_sched_rt01.c:72: TFAIL: echo rt_period_us+1 > /proc/sys/kernel/sched_rt_runtime_us invalid retval 1: SUCCESS (0) HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fc6484e1fb https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=079be8fc6309 Summary: passed 2 failed 3 broken 0 skipped 0 warnings 0 INFO: ltp-pan reported some tests FAIL LTP Version: 20230929-406-gcbc2d0568 INFO: Test end time: Tue Mar 12 11:52:21 UTC 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2057734/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2060213] [NEW] "apt failed to download packages, retrying in 10s..." results in " Unable to acquire the dpkg frontend lock"
Public bug reported: logfile: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/armhf/b/balsa/20240404_081820_ad372@/log.gz pertinent log messages: ``` 883s Get:204 http://ftpmaster.internal/ubuntu noble-proposed/universe armhf xvfb armhf 2:21.1.11-2ubuntu2 [738 kB] 935s autopkgtest: WARNING: apt failed to download packages, retrying in 10s... 954s E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 763 (apt-get) 954s E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? 955s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 957s Reading package lists... 958s Building dependency tree... ``` It perhaps looks like in a setup script, whilst sleeping before a retry, another process starts an apt-get command which causes the script to fail after the sleep. Or something along those lines. ** Affects: auto-package-testing Importance: Undecided Status: New ** Description changed: logfile: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/armhf/b/balsa/20240404_081820_ad372@/log.gz pertinent log messages: ``` 883s Get:204 http://ftpmaster.internal/ubuntu noble-proposed/universe armhf xvfb armhf 2:21.1.11-2ubuntu2 [738 kB] 935s autopkgtest: WARNING: apt failed to download packages, retrying in 10s... 954s E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 763 (apt-get) 954s E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? 955s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 957s Reading package lists... 958s Building dependency tree... ``` - It perhaps looks like in setup-testbed, whilst sleeping before a retry, + It perhaps looks like in a setup script, whilst sleeping before a retry, another process starts an apt-get command which causes the script to fail after the sleep. Or something along those lines. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2060213 Title: "apt failed to download packages, retrying in 10s..." results in " Unable to acquire the dpkg frontend lock" Status in Auto Package Testing: New Bug description: logfile: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/armhf/b/balsa/20240404_081820_ad372@/log.gz pertinent log messages: ``` 883s Get:204 http://ftpmaster.internal/ubuntu noble-proposed/universe armhf xvfb armhf 2:21.1.11-2ubuntu2 [738 kB] 935s autopkgtest: WARNING: apt failed to download packages, retrying in 10s... 954s E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 763 (apt-get) 954s E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? 955s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs 957s Reading package lists... 958s Building dependency tree... ``` It perhaps looks like in a setup script, whilst sleeping before a retry, another process starts an apt-get command which causes the script to fail after the sleep. Or something along those lines. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2060213/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
** Changed in: autopkgtest (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in Auto Package Testing: Invalid Status in autopkgtest package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
