Ordering issue with dracut 110

[guilherme-puida]

Dracut 110 changed the ordering of systemd-crypsetup to 71. This seems to make stuff not work anymore:

dracut[I]: *** Including module: clevis ***
Failed to add dependency on unit: Unit cryptsetup.target does not exist

Readding cryptsetup.target to inst_multiple (like in d7a2f38) seems to fix the issue, but I'm not sure if this is the correct approach.

Tested on a recent daily build of Ubuntu Server 26.04.

ii  clevis-dracut                     21-1                                       amd64        Clevis integration for dracut
ii  dracut                            110-3ubuntu1                               all          Initramfs generator using udev

# ls -1Fv /usr/lib/dracut/modules.d/ | grep -E 'clevis|cryptsetup'
60clevis/
60clevis-pin-null/
60clevis-pin-sss/
60clevis-pin-tang/
60clevis-pin-tpm2/
71systemd-cryptsetup/

[baierjan]

I hit the same issue on recent openSUSE Tumbleweed and openSUSE MicroOS as well. A quick workaround without editing the modules is to create /etc/dracut.conf.d/50-clevis-fix.conf with:

install_items+=" /usr/lib/systemd/system/cryptsetup.target "

[oldium]

Maybe the easiest “fix” would be to get this line back: https://github.com/latchset/clevis/pull/501/changes#diff-d823484a636cfc7f6250b4370188f80e85a1168b201aa26079ca19361a6aec00L35

[guilherme-puida]

FTR: I fixed this in Ubuntu by reintroducing cryptsetup.target in inst_multiple.

https://git.launchpad.net/ubuntu/+source/clevis/commit/?id=e601719777f3f14ad46efe65b5f133453069872a

This was uploaded as clevis 20-1ubuntu2, which will be the version in the next Ubuntu LTS release.

[oldium]

FTR: I fixed this in Ubuntu by reintroducing cryptsetup.target in inst_multiple.

https://git.launchpad.net/ubuntu/+source/clevis/commit/?id=e601719777f3f14ad46efe65b5f133453069872a

This was uploaded as clevis 20-1ubuntu2, which will be the version in the next Ubuntu LTS release.

I also think that would be the simplest solution. The installation follows the same sequence as the module number, so if the clevis is numbered 50 and systemd-cryptsetup has ranged between 01 and 90 over the past two years (yes, seriously), we have no other choice but to install the file manually.

[oldium]

I will prepare a pull request later today, if nobody is faster than me 😁

[oldium]

I have checked why #501 with Dracut v102 worked on FC40 (90systemd-cryptsetup) and it was because there was 00systemd which installed also cryptsetup.target... Aargh...

[oldium]

The critical change in Dracut was in version v104 dracut-ng/dracut-ng@ad52085, which removed duplicate install of cryptsetup.target from 00systemd (later renamed to 10systemd). Then it was just a question about the exact module number of systemd-cryptsetup.

[oldium]

Reported here in Dracut project: dracut-ng/dracut-ng#2395

[oldium]

Fixed in #549