On Ubuntu 18.04, I can get secondary volumes with LUKS to unlock with clevis at boot to work but root volumes are giving me issues unlocking at bootup and I think the issue is related to dracut.
Anyone have an idea what is wrong or if this is a bug or how I can check logs for dracut to make sure it is working properly with clevis? Thanks,
/etc/fstab
root@cisadmin-VirtualBox:~# cat /etc/fstab
# /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/sda5_crypt / ext4 defaults,_netdev 0 2
# /boot was on /dev/sda1 during installation
UUID=45c8c1b2-3558-43d1-9e41-cf49dccf4ab2 /boot ext4 defaults 0 2
/swapfile none swap sw 0 0
On Ubuntu 18.04, I can get secondary volumes with LUKS to unlock with clevis at boot to work but root volumes are giving me issues unlocking at bootup and I think the issue is related to dracut.
Anyone have an idea what is wrong or if this is a bug or how I can check logs for dracut to make sure it is working properly with clevis? Thanks,
/etc/fstab
/etc/crypttab