Cannot unlock encrypted root after upgrading to 22.04 - no prompt to enter a password

[Jesse Johnson]

Followup to https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1979159 whose fix does not seem to be applying to upgrades using the official Ubuntu 22.04 upgrade pop-up notification.

I seem to have encountered this bug during a upgrade via the official upgrade pop-up notification.

Has the fix in 1979159 in fact been moved to -updates and would be included in a regular installation?

I upgraded a Ubuntu 20.04 desktop PC after it received the Ubuntu 22.04 upgrade pop-up notification, but could not unlock my encrypted root after reboot, instead receiving an error to the effect of "Gave up waiting for root device, ubuntu--vg-root does not exist" (not exact wording).

The workaround in 1979159 via live boot + chroot did not seem to work, and neither did running update + dist-upgrade which I hoped to resolve the OpenSSL issue, though I was able to unlock manually via live boot. I was pressed for time so did not pursue it further and did a full reinstall via a backup.

I did not enable `jammy-proposed` for this failed upgrade as I did in my initial successful testing of the 1979159 fix, which makes me suspect this fix is not being included in upgrades done via `ubuntu-release-upgrader` or `do-release-upgrade`.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.13
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 17 15:06:26 2022
InstallationDate: Installed on 2022-08-17 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

[Steve Langasek (vorlon)]

Reassigning this bug to cryptsetup. ubuntu-release-upgrader does not unlock encrypted devices.

You ask if the fix for bug #1979159 has been released to -updates and it has. However, you have given us no reason to think that you are affected by the same bug as the submitter of that bug report, which to our knowledge does not affect any users that have installed Ubuntu at any point using the default cryptsetup options.

There is an unrelated bug that has been filed, reporting that a kernel upgrade has made cryptsetup unlocking unreliable at boot. It is possible you are/were affected by this bug.

https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1986623

> I was pressed for time so did not pursue it further and did a full reinstall via a backup.

That is unfortunate, as your bug report includes no debugging information that would allow us to pinpoint the nature of the issue you experienced. So if you are no longer able to reproduce the bug, we have nothing to go on. All of our own upgrade tests have shown cryptsetup to work at boot after upgrade.

I will leave this bug report in 'incomplete' status, but if no further information is forthcoming, it will eventually close automatically.

[Jesse Johnson (holocronweaver)]

> does not affect any users that have installed Ubuntu at any point using the default cryptsetup options.

I don't see that mentioned in the bug description - would be worth updating the description near the top if possible so others know the bug scope. I interpreted the Ubuntu 20.04 -> 22.04 part of the test plan to mean this affected encrypted roots with older encryption protocols Ubuntu once used.

IIRC I used the default cryptsetup options in my original install of 18.04, which upgraded fine to 20.04 but failed to upgrade to 22.04.

> There is an unrelated bug that has been filed, reporting that a kernel upgrade has made cryptsetup unlocking unreliable at boot. It is possible you are/were affected by this bug. https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1986623

It may be related, but it is not the same behavior I encountered. In my case I never received a prompt to enter a password, instead receiving the error "Gave up waiting for root device, ubuntu--vg-root does not exist".

It seems to be the same issue as this Ask Ubuntu query, which several people have had to deal with for the 20.04 to 22.04 upgrade, so this is likely not a one-off problem:

https://askubuntu.com/q/1403753/29444

I had a few errors during upgrade which I saved (see attached), but I don't think they are related to the partition encryption issue.

> That is unfortunate, as your bug report includes no debugging information that would allow us to pinpoint the nature of the issue you experienced.

True, but I suspect I won't be the only one to encounter this so wanted to give a heads up to the Ubuntu dev time, and a place for anyone else to quickly chime in that has encountered the issue as part of the ongoing upgrades.

If someone has more diagnostic info please create a new bug report and link this as a duplicate. I have another dozen or so systems to upgrade and I'm holding off doing so until this is resolved.

I will try to replicate one of my existing systems on a test box and run the upgrade to see if I can reproduce the issue and add more debug info.

[Benjamin Drung (bdrung)]

The "AttributeError: 'DistUpgradeController' object has no attribute 'tasks'" error is bug #1969786.

It would be perfect if you could reproduce your upgrade issue.

[Launchpad Janitor (janitor)]

[Expired for cryptsetup (Ubuntu) because there has been no activity for 60 days.]