canonical-ubuntu-qa team mailing list archive

[Paride Legovini <2109845@xxxxxxxxxxxxxxxxxx>]

I think autopkgtest should limit changes to the testbed system when
running tests. Bugs that are the opposite of this one ("I ran test X on
image Y, but it fails because autopkgtest modified the image") are more
annoying.

If you want to avoid preparing images for autopkgtest, you can try
passing

  --setup-commands=setup-testbed

This will run /usr/share/autopkgtest/setup-commands/setup-testbed in the
testbed before executing the test. That's the main script that does
customization for autopkgtest specific images, including uninstalling
unattended-upgrades.

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
Matching subscriptions: ubuntu-qa-bugs
https://bugs.launchpad.net/bugs/2109845

Title:
  autopkgtest should disable unattended-upgrades and related services

Status in autopkgtest package in Ubuntu:
  New

Bug description:
  autopkgtest should disable or remove unattended-upgrades and related
  services, to avoid silly lock issues like this one from aborting a
  potentially expensive/long test:

  autopkgtest [11:17:08]: test systemd-socket-activation: preparing testbed
  E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 109391 (unattended-upgr)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2109845/+subscriptions