When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues.
This is fixed in the lvm2 version 2.03.23 upstream release.
When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues.
This is fixed in the lvm2 version 2.03.23 upstream release.
Please consider backporting this patch for Noble.
Upstream PR: https:/ /gitlab. com/lvmteam/ lvm2/-/ merge_requests/ 3 91bd361369423d7 309358f6c1
Upstream commit: 25ef7a7b1a876f4