clevis
clevis copied to clipboard
Dracut unlocker + tang pin lacks required basename binary on Fedora 31
This is the boot log after the bind:
[ OK ] Reached target Paths.
[ OK ] Found device Samsung_SSD_850_PRO_512GB 3.
Starting Cryptography Setu…f146-4155-a920-5fe04b92f239...
[ 2.656671] dracut-initqueue[539]: Error communicating with the server!
[ 11.158957] dracut-initqueue[539]: /lib/dracut/hooks/initqueue/settled/99-nm-run.sh: line 13: basename: command not found
[ 11.245226] dracut-initqueue[539]: Error communicating with the server!
[ 11.884868] dracut-initqueue[539]: Error communicating with the server!
[ 17.938212] dracut-initqueue[539]: /lib/dracut/hooks/initqueue/settled/99-nm-run.sh: line 13: basename: command not found
[ 18.039129] dracut-initqueue[539]: Error communicating with the server!
[ 18.678655] dracut-initqueue[539]: Error communicating with the server!
[ 24.729037] dracut-initqueue[539]: /lib/dracut/hooks/initqueue/settled/99-nm-run.sh: line 13: basename: command not found
[ 24.828738] dracut-initqueue[539]: Error communicating with the server!
[ 25.472209] dracut-initqueue[539]: Error communicating with the server!
[ 31.525300] dracut-initqueue[539]: /lib/dracut/hooks/initqueue/settled/99-nm-run.sh: line 13: basename: command not found
[ 31.620314] dracut-initqueue[539]: Error communicating with the server!
[ 32.273268] dracut-initqueue[539]: Error communicating with the server!
[...]
Then this repeats until I manually unlock the disk.
Required libs and binaries are built as explained in #136
As I mentioned in #147, I think this should be fixed in dracut. Could you try this scratch build and see if it resolves the issue for you? https://koji.fedoraproject.org/koji/taskinfo?taskID=39421879
It should contain https://github.com/dracutdevs/dracut/commit/5e0f8c8a4ced36268d0077acafa1db2402776fa6
Yup. Had to force the install with --replacepkgs --replacefiles but after that, IP based unlock does work without basename.
When are these updates expected to come down to Fedora stable?
Thanks for testing. I will submit the PR there and hopefully a dracut maintainer will pick it up soon; afterwards it will be available in testing and then, stable.
Thanks a lot. Shall I close this issue + the corresponding PR then?
I think we should leave the issue open until it gets fixed in Fedora, but feel free to close the PR.
Fair enough :)