Closed ACiDGRiM closed 1 year ago
This seems more like a dracut issue, right? Did you configure clevis to unlock the encrypted device?
Could you please detail the steps followed so that we can have an idea of the issue?
I'd agree it could a dracut issue but it only happened after installing clevis, which suggests that the clevis script is hanging
1) install packages 2) bind root disk luks to tang server 3) test dracut network configuration via rd.break and confirm ping 4) boot into system and add _netdev to root crypttab and fstab 5) run dracut -f and reboot 6) initramfs environment hangs at initqueue
I can confirm in the initramfs the crypttab lists the root luks volume. Can you at least give me a pointer on how to manually trigger the askpass sequence and run the clevis dracut unlocker so I can start to rule-out or identify where it's breaking?
What options do you have in your crypttab? Do you have something like _netdev
?
I just saw that you have it, from step 4. Please, remove it, recreate your initramfs and try again, to see if it helps.
I'm going to reinstall the system from scratch, I have frequent kernel panics before clevis and this was an attempt to bypass the boot prompt while the kernel issue was investigated. I'll update if this occurs or not on a newly deployed and updated system.
huh, it actually boots successfully and unlocks the drives with _netdev removed.
Also a point I see in the clevis dracut modulesetup it mentions that rd.neednet is supposed to be turned on, but I have to set it in the kernel cmdline for it to activate the network connection.
I've installed the clevis and clevis-dracut packages on a Centos 9 system and after rebuilding the initramfs with dracut it hangs on the step "starting initqueue hooks"
I've made the following changes to ensure my system has an IP address on boot:
I tried to remove the rd.luks.uuid from the boot cmd and it didn't change anything when dracut crashes to the recovery console, I can source clevis-luks-common-functions and unlock the drive manually with
clevis_luks_ unlock_device /dev/sdd3 | cryptsetup luksOpen /dev/sdd3 luks-root
and then exiting the recovery console to continue booting.