[Bug 1987452] Re: do-release-upgrade without the latest version of apt in focal or groovy will crash

Steve Langasek 1987452 at bugs.launchpad.net
Fri Sep 2 23:50:21 UTC 2022


Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:22.04.14
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-release-upgrader (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1987452

Title:
  do-release-upgrade without the latest version of apt in focal or
  groovy will crash

Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed

Bug description:
  Impact
  ------
  There are many crash reports in the Ubuntu Error tracker (https://errors.ubuntu.com/problem/d7622e91a2afe1c1fc697f6717d45146525825c3 for one) where people experience a crash trying to upgrade from Groovy (and Focal) to Jammy due to having an old version of apt installed. While the release upgrade process ensures they have the latest version of packages installed its possible they don't have -updates enabled or their apt list files are out of date. Whatever the reason this can keep people stuck on a potentially EoL release.

  Test Case
  ---------
  1) On an Ubuntu 20.04 (or Ubuntu 20.10) system install the version of libapt-pkg6.0 and apt from the release pocket (not -updates).
  2) Disable the -updates pocket in /etc/apt/sources.list. (Or rm /var/lib/apt/lists/* .)
  3) Run do-release-upgrade
  4) Observe a crash early in the upgrade process

  With the version of ubuntu-release-upgrader from -proposed (testable
  by using do-release-upgrade -p) the release upgrade will not crash and
  instead you will be notified to install the newer version of apt and
  libapt-pkg6.0. The message will look like the following:

  "Reading state information... Done

  Required depends is not installed

  The required dependency 'apt (>= 2.0.4)' is not installed."

  Regression Potential
  --------------------
  If the Depends line is improperly formatted the upgrade process could end up crashing in a different way.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.13
  ProcVersionSignature: Ubuntu 5.8.0-63.71-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  Date: Tue Aug 23 14:47:18 2022
  DuplicateSignature: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
  ExecutablePath: /usr/bin/do-release-upgrade
  ExecutableTimestamp: 1621013264
  InstallationDate: Installed on 2022-08-03 (20 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 -s /tmp/ubuntu-release-upgrader-fpldmaum/jammy --mode=server --frontend=DistUpgradeViewText
  ProcCwd: /tmp/ubuntu-release-upgrader-fpldmaum
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.6-0ubuntu1
  PythonArgs: ['/usr/bin/do-release-upgrade', '--mode=server', '--frontend=DistUpgradeViewText']
  PythonDetails: N/ASourcePackage: ubuntu-release-upgrader
  Title: do-release-upgrade crashed with apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
  Traceback: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
  UpgradeStatus: Upgraded to groovy on 2022-08-23 (0 days ago)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1987452/+subscriptions




More information about the foundations-bugs mailing list