broken installation while mirror syncing new kernel packages

[Andre Ruiz]

A new kernel package for jammy was released 3 hours ago. It is probably being synced to mirrors right now.

It can be seen at https://launchpad.net/ubuntu/+source/linux-meta:

5.15.0.76.74 updates (main) 3 hours ago

A little before that, I was deploying 10 Jammy machines in maas, without any problem. After that, I started having all 10 machines fail deployment. The reason is that curtin will fail package updates (complete log attached). This is the important part:

==========================================8<---------------------------------------------------
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with allowed return codes [0] (capture=False)
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable
 linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed
                       Depends: linux-modules-extra-5.15.0-76-generic but it is not installable
                       Recommends: thermald but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
==========================================8<---------------------------------------------------

The repository being used is "http://archive.ubuntu.com/ubuntu jammy/main"

It may be the case that there is still a partial mirror there, but it should not break and instead just use the latest available version while the new one is not completely avalable.

I'm not sure this is only valid for linux kernel packages (maybe this is a general problem with any package) but I'm opening to linux-meta since it happened with linux in this case.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Matt (eioq3wjekqnmlwerasdhjkl412p)]

Ditto. Looks like 2 packages are unavailable:
linux-modules-extra-5.15.0-76-generic
linux-modules-5.15.0-76-generic

===== sudo apt install --download-only linux-modules-extra-5.15.0-76-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-modules-extra-5.15.0-76-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'linux-modules-extra-5.15.0-76-generic' has no installation candidate
=====

===== sudo apt install --download-only linux-modules-5.15.0-76-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-modules-5.15.0-76-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'linux-modules-5.15.0-76-generic' has no installation candidate
=====

[Chris Guiver (guiverc)]

This maybe being experienced by a number of end-users, I've now seen support requests (eg. https://askubuntu.com/questions/1475121/broken-linux-generic-or-linux-headers-generic-dependencies on an Server install being just one) ; but that's (my) opinion/suspicion only.

another (non-install this time) being https://askubuntu.com/questions/1475132/linux-image-5-15-0-76-generic-not-installing-due-to-missing-packages-on-ubuntu-2

[Horst Platz (hp-localhorst)]

This behavior is on all my servers approximately 15

:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy

:~# apt-get dist-upgrade
[...]
The following packages have been kept back:
  linux-generic linux-headers-generic linux-image-generic
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

:~# apt-get install linux-generic linux-headers-generic linux-image-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable
 linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed
                       Depends: linux-modules-extra-5.15.0-76-generic but it is not installable
E: Unable to correct problems, you have held broken packages.

:~# apt-cache search linux-modules-extra-5.15.0-76-generic
-> with no result

[Maarten (crcerror)]

autoinstall/cloud-init is failing for the same reason at the moment.

[Daniel Isaksen (isadanbn)]

Also seeing this during installation of focal (20.04).

Log excerpt:

Jun 28 09:19:04 in-target: Reading package lists...
Jun 28 09:19:04 in-target:
Jun 28 09:19:04 in-target: Building dependency tree...
Jun 28 09:19:04 in-target:
Jun 28 09:19:04 in-target: Reading state information...
Jun 28 09:19:04 in-target: Some packages could not be installed. This may mean that you have
Jun 28 09:19:04 in-target: requested an impossible situation or if you are using the unstable
Jun 28 09:19:04 in-target: distribution that some required packages have not yet been created
Jun 28 09:19:04 in-target: or been moved out of Incoming.
Jun 28 09:19:04 in-target: The following information may help to resolve the situation:
Jun 28 09:19:04 in-target:
Jun 28 09:19:04 in-target: The following packages have unmet dependencies:
Jun 28 09:19:04 in-target: linux-image-generic-hwe-20.04 : Depends: linux-image-5.15.0-76-generic but it is not going to be installed
Jun 28 09:19:04 in-target: Depends: linux-modules-extra-5.15.0-76-generic but it is not installable
Jun 28 09:19:04 in-target: E: Unable to correct problems, you have held broken packages.
Jun 28 09:19:04 base-installer: dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Jun 28 09:19:04 /bin/in-target: warning: /target/etc/mtab won't be updated since it is a symlink.
Jun 28 09:19:04 in-target: Reading package lists...
Jun 28 09:19:04 in-target:
Jun 28 09:19:04 in-target: Building dependency tree...
Jun 28 09:19:04 in-target:
Jun 28 09:19:04 in-target: Reading state information...
Jun 28 09:19:04 in-target: Some packages could not be installed. This may mean that you have
Jun 28 09:19:04 in-target: requested an impossible situation or if you are using the unstable
Jun 28 09:19:04 in-target: distribution that some required packages have not yet been created
Jun 28 09:19:04 in-target: or been moved out of Incoming.
Jun 28 09:19:04 in-target: The following information may help to resolve the situation:
Jun 28 09:19:04 in-target:
Jun 28 09:19:04 in-target: The following packages have unmet dependencies:
Jun 28 09:19:04 in-target: linux-headers-generic-hwe-20.04 : Depends: linux-headers-5.15.0-76-generic but it is not installable
Jun 28 09:19:04 in-target: E: Unable to correct problems, you have held broken packages.
Jun 28 09:19:04 base-installer: error: exiting on error base-installer/kernel/failed-install
Jun 28 09:19:58 main-menu[400]: WARNING **: Configuring 'bootstrap-base' failed with error code 30
Jun 28 09:19:58 main-menu[400]: WARNING **: Menu item 'bootstrap-base' failed.

[Andre Ruiz (andre-ruiz)]

It seems like it was not a partial mirror problem but a partial release of kernel updates packages because of some issue in the release process. It was detected by the kernel team and should be fixed by now, at least for jammy.

[Feather (internet-maintenance)]

I'm still having problems installing 'linux-image-5.15.0-76-generic-dbgsym':

Unable to locate package linux-image-5.15.0-76-generic-dbgsym
Couldn't find any package by glob 'linux-image-5.15.0-76-generic-dbgsym'

[Adrian Vill (goat-whisper)]

Started experiencing this behavior yesterday evening (Jun 29) with 22.04.2 GA see attached image. Our 22.04.2 HWE instance is still functional at time of writing.