Ubuntu 19.04-> 19.10: Problem with encrypted swap partition

Hi.
I had a bad moment when (belatedly) upgrading Ubuntu 19.04-> 19.10 last weekend.

The upgrade process

do-release-upgrade

complained that it couldn't read my encrypted swap partition and didn't create initrd.img-5.3.0-46-generic in /boot.

In fact I had a broken symlink for

initrd.img -> initrd.img-5.3.0-46-generic

until the very end of the update when (happy days) the installer *did* create initrd.img-5.3.0-46-generic.

(Beer was consumed.)

Can I assume that the same "end of update" fix will work when I upgrade to 20.04 LTS?

My /etc/fstab
Code:# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=91ee4872-1d44-431b-b56e-62a0c8e5e5d1 /boot ext2 defaults 0 2
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0My /etc/crypttab
Code:sda5_crypt UUID=f06d7a31-34bb-4911-99b0-d91c272350a5 none luks,discard
cryptswap1 UUID=07ebc8c9-dd82-4e61-b64b-160e0b63a811 /dev/urandom swap,offset=1024,cipher=aes-xts-plain64Joseph Borg posted that the best way to deal with this problem is

Quote:

After you've run `do-release-upgrade -d`: 1) sudo swapoff -a 2) sudo cryptsetup remove cryptswap1 3) Edit `/etc/fstab`, remove the line mentioning cryptswap1 4) Edit `/etc/crypttab `, remove the line mentioning cryptswap1 5) sudo update-initramfs -u 6) sudo update-grub 7) Reboot

Or maybe not a problem at all?

Advice very much appreciated.

John