canonical-ubuntu-qa team mailing list archive

[Andreas Hasenack <2115731@xxxxxxxxxxxxxxxxxx>]

>   * I don't exactly know what changed to now reach that state, and what made it work before. Probably 
> something around the testbed preparation in `autopkgtest` itself.

Perhaps there was a kernel update that requires a reboot now, and that
wasn't the case before? Perhaps the base OS you were using before was
already up-to-date, and it was just by chance that you didn't need to
reboot?

Thanks for digging into this!

-- 
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/2115731

Title:
  upgrade-testing is broken with autopkgtest >5.47

Status in Auto Upgrade Testing:
  Fix Released
Status in autopkgtest package in Ubuntu:
  Won't Fix
Status in autopkgtest source package in Jammy:
  Won't Fix
Status in autopkgtest source package in Noble:
  Won't Fix
Status in autopkgtest source package in Oracular:
  Won't Fix
Status in autopkgtest source package in Plucky:
  Won't Fix
Status in autopkgtest source package in Questing:
  Won't Fix

Bug description:
  upgrade testing code repo: https://github.com/canonical/auto-upgrade-testing
  upgrade testing profiles repo: https://code.launchpad.net/auto-upgrade-testing-specifications/

  Clone them both side to side, then use the following reproducer:

  ```
  python3 -m upgrade_testing.command_line -c ../auto-upgrade-testing-specifications/profiles/ubuntu-noble-oracular-basic-amd64_qemu.yaml --provision  --adt-args='--timeout-factor=10 -d' --results-dir /tmp/upgrade_tests
  ```

  The upgrade should fail, apparently because now autopkgtest is a bit more eager to reboot when a package needs it before running the tests, and then upgrade-testing checks right away if it's booting on the right system, which is obviously not the case.
  The fix might actually be in upgrade testing code, because all that interaction between autopkgtest and that code has always been very brittle, but I wanted to track the regression in a bug anyway (SRU LP: #2106167).

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-upgrade-testing/+bug/2115731/+subscriptions