Since the fstab manpage documents the UUID syntax, how do you justify your claim that "in /etc/fstab you must use /dev/mapper/<name> entries"?
Actually, it seems to me that you misunderstood the point of the bugreport. This bug is about cryptsetup, since cryptsetup is the application that fails to parse a valid /etc/fstab.
To reproduce the problem, set up a system with encrypted root and encrypted swap and use the LABEL= or UUID= syntax in /etc/fstab and /etc/initramfs-tools/conf.d/resume. Your system will not boot.
Then try the same without using encryption. The system will boot fine.
Since the fstab manpage documents the UUID syntax, how do you justify your claim that "in /etc/fstab you must use /dev/mapper/<name> entries"?
Actually, it seems to me that you misunderstood the point of the bugreport. This bug is about cryptsetup, since cryptsetup is the application that fails to parse a valid /etc/fstab.
To reproduce the problem, set up a system with encrypted root and encrypted swap and use the LABEL= or UUID= syntax in /etc/fstab and /etc/initramfs- tools/conf. d/resume. Your system will not boot.
Then try the same without using encryption. The system will boot fine.