canonical-ubuntu-qa team mailing list archive

[Tim Andersson <2060213@xxxxxxxxxxxxxxxxxx>]

so, @paride , I checked and unattended upgrades are definitely not installed on our lxc runners:
```
root@autopkgtest-lxd-xxkcjb:~# apt list --installed | grep upgrade

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

root@autopkgtest-lxd-xxkcj
```
and I can see it removed in image creation:
```
Removing unattended-upgrades (2.9.1+nmu4ubuntu1) ...
```
However, I see this failure in prod:
```
Purging configuration files for unattended-upgrades (2.9.1+nmu4ubuntu1) ...
dpkg: warning: while removing unattended-upgrades, directory '/var/log/unattended-upgrades' not empty so not removed
```
I created my own image with autopkgtest-build-lxd.

But that seems to be fine, I boot a container from this image, and
unattended-upgrades is 100% not installed.

So, the issue isn't unattended-upgrades. What else could be running apt-
get in the background?

-- 
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:
  In Progress

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