canonical-ubuntu-qa team mailing list archive

[Paride Legovini <2009052@xxxxxxxxxxxxxxxxxx>]

Thanks, this definitely shouldn't happen. From the log you linked I see:

Unpacking linux-generic (6.1.0.16.16) over (5.19.0.23.22) ...

so the previously installed version of linux-generic was 5.19.0.23.22.
However I don't see that version published to lunar-release in the
linux-meta publication history:

https://launchpad.net/ubuntu/+source/linux-
meta/+publishinghistory?batch=300

which means we already had kernel packages from proposed, with a higher
version number than the versions available in lunar and lunar-updates.
In this situation packages *are* updated from -proposed [*]. (Worth
noting that this is not a kernel specific thing.)

Now, this explains why the upgrade happens. It doesn't explain why we
ended up with kernel packages not available in the release/-updates
pockets in the ADT images. Two possible explanations:

1. Kernel packages were published to lunar-proposed, ended up in the ADT
images, but were then pulled from the archive. I can't see this
happening in the linux-meta publication history linked above.

2. When we created the Lunar images at the beginning of the cycle we
included 0-day sru Kinetic kernel packages which were not available in
lunar yet. Again I can't recognize this happening from the publication
history: the first kinetic-updates kernel is from December 2022, way
after we created the images.

I am not sure we'll ever know. In any case what may prevent this from
happening is fixing the build-adt-image (from autopkgtest-cloud) so that
it forces only packages from the target release to be installed,
possibly downgrading (via Pin-Priority > 1000).

[*] See the "Sometimes the installed version of a package is more recent
than the version belonging to the target release [...]" sentence in
apt_preferences(5).

** Changed in: auto-package-testing
       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/2009052

Title:
  proposed kernel is installed when a trigger is from proposed

Status in Auto Package Testing:
  Confirmed

Bug description:
  While investigating propoposed-migration of sphinx-rtd-theme and
  pillow, it was found that the autopkgtests of python-fabio would
  likely fail when tested with any package from proposed, even yabasic,
  a completely unrelated package.

  https://autopkgtest.ubuntu.com/packages/python-fabio/lunar/amd64

  From one of the failed logs
  https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/p/python-fabio/20230301_100331_bc80f@/log.gz

  It appears the proposed kernel is installed when a trigger is from
  proposed, but not when running a migration-reference/0 test.  Is this
  a bug or a feature?

  The following additional packages will be installed:
    linux-headers-6.1.0-16 linux-headers-6.1.0-16-generic linux-headers-generic
    linux-headers-virtual linux-image-6.1.0-16-generic linux-image-generic
    linux-image-virtual linux-modules-6.1.0-16-generic
    linux-modules-extra-6.1.0-16-generic linux-virtual
  Suggested packages:
    fdutils linux-doc | linux-source-6.1.0 linux-tools
  Recommended packages:
    thermald
  The following NEW packages will be installed:
    linux-headers-6.1.0-16 linux-headers-6.1.0-16-generic
    linux-image-6.1.0-16-generic linux-modules-6.1.0-16-generic
    linux-modules-extra-6.1.0-16-generic
  The following packages will be upgraded:
    linux-generic linux-headers-generic linux-headers-virtual
    linux-image-generic linux-image-virtual linux-virtual
  6 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
  Need to get 128 MB of archives.

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