[Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules

[Steve Langasek]

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: Triaged => Invalid

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

** Changed in: ubuntu-release-upgrader (Ubuntu Jammy)
     Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
  modules

Status in Ubuntu on IBM z Systems:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader source package in Jammy:
  In Progress

Bug description:
  [Impact]
  Upgrade from Ubuntu 21.10 to 22.4 fails if pam_tally is present in the system's PAM config

  I run do-release-upgrade and I got a message upgrade completed with
  errors. I rebooted the server and it is now in an undefined state
  between 21.10 and 22.04. Not all packages have been installed. I
  attach apt log and output of some commands:

  root at tuxmaker:~# cat /etc/os-release
  PRETTY_NAME="Ubuntu 21.10"
  NAME="Ubuntu"
  VERSION_ID="21.10"
  VERSION="21.10 (Impish Indri)"
  VERSION_CODENAME=impish
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/"
  SUPPORT_URL="https://help.ubuntu.com/"
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
  UBUNTU_CODENAME=impish

  root at tuxmaker:~# do-release-upgrade
  Checking for a new Ubuntu release
  Please install all available updates for your release before upgrading.

  root at tuxmaker:~# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 1.4.0-11ubuntu2 is installed
                    Recommends: update-motd but it is not installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

  root at tuxmaker:~# apt --fix-broken install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
    libpam-modules
  The following packages will be upgraded:
    libpam-modules
  1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded.
  4 not fully installed or removed.
  Need to get 0 B/279 kB of archives.
  After this operation, 1,024 B disk space will be freed.
  Do you want to continue? [Y/n] y
  Preconfiguring packages ...
  (Reading database ... 401827 files and directories currently installed.)
  Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ...
  dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack):
   new libpam-modules:s390x package pre-installation script subprocess returned error exit status 2
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Contact Information = ppohl at de.ibm.com

  [Test plan]
  Test 1
  ------ 
  The pre-build.sh script run prior to generation of the upload tarball runs the test suite which includes an added test for this quirk to verify its correct operation.

  Test 2
  ------
  Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed.

  Verify that the upgrade completes successfully with the addition of
  the new quirk, which should have no effect on a default install.

  Test 3
  ------
  On an impish system, run 'do-release-upgrade -p' to use the tarball from -proposed.  Verify that the upgrade completes successfully.

  
  [Where problems could occur]
  The addition of a quirk could prevent some users from upgrading, in which case a further SRU will be necessary.  The new code is run very early in the upgrader and it should not be possible for the new code to leave the system in an inconsistent state mid-upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977493/+subscriptions