Upgrade from 18.04 to 20.04 installs gke kernel

Bug #2028306 reported by Felix Rieger
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

- Upgraded 18.04 to 20.04 using the graphical upgrader
- Upgrade seems to have installed the gke kernel, thus wrong graphics driver and no Wifi connectivity
- Upon removing the gke kernel, system runs as expected

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.41
ProcVersionSignature: Ubuntu 5.4.0-153.170-generic 5.4.235
Uname: Linux 5.4.0-153-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 20 21:48:09 2023
InstallationDate: Installed on 2020-02-05 (1261 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2023-07-20 (0 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
Felix Rieger (riegerf) wrote :
tags: added: foundations-todo
Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → High
Revision history for this message
Steve Langasek (vorlon) wrote :

https://launchpadlibrarian.net/678177756/VarLogDistupgradeAptlog.txt shows the user did have the correct metapackage installed prior to upgrade.

MarkInstall linux-generic-hwe-18.04:amd64 < 5.4.0.150.167~18.04.121 -> 5.4.0.153.150 @ii umU Ib > FU=0
  Installing linux-generic as Depends of linux-generic-hwe-18.04
    MarkInstall linux-generic:amd64 < none -> 5.4.0.153.150 @un uN > FU=0

https://launchpadlibrarian.net/678177763/VarLogDistupgradeMainlog.txt shows that u-r-u is pulling in linux-gke anyway:

2023-07-20 19:50:06,656 INFO installing linux metapackage: linux-gke
2023-07-20 19:50:06,656 DEBUG Installing 'linux-gke' (linux metapackage may have been accidentally uninstalled)

This is because there were gke packages present on the system before the upgrade.

  MarkPurge linux-modules-5.3.0-1045-gke:amd64 < 5.3.0-1045.48 @ii mK > FU=1
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) linux-image-unsigned-5.3.0-1045-gke:amd64 < 5.3.0-1045.48 @ii mK Ib >
Broken linux-image-unsigned-5.3.0-1045-gke:amd64 Depends on linux-modules-5.3.0-1045-gke:amd64 < 5.3.0-1045.48 @ii pmP >
  Considering linux-modules-5.3.0-1045-gke:amd64 10001 as a solution to linux-image-unsigned-5.3.0-1045-gke:amd64 -2
  Removing linux-image-unsigned-5.3.0-1045-gke:amd64 rather than change linux-modules-5.3.0-1045-gke:amd64
  MarkDelete linux-image-unsigned-5.3.0-1045-gke:amd64 < 5.3.0-1045.48 @ii mK Ib > FU=0
Done

u-r-u tries to make sure that the metapackage for the "most recent" kernel is present.

It seems to figure this wrong because it doesn't know how to handle the hwe-named metapackages, where the hwe-* suffix doesn't match the per-ABI package name pattern.

So it appears to be the combination of having a stale gke kernel installed (5.3, which is newer than the version in Ubuntu 18.04 LTS but older than the version in Ubuntu 20.04 LTS), plus the use of an HWE kernel, that triggers this.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Triaged
Revision history for this message
Steve Langasek (vorlon) wrote :

The GKE kernel being present on the system prior to upgrade was not a problem because it was a lower version than the HWE kernel installed (5.3 vs 5.4).

Changed in ubuntu-release-upgrader (Ubuntu):
importance: High → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.