Thank you for your quick answer.

a1. Why no network configured ? I think that clevis initramfs unlock
would just use DHCP and get a lease from the DHCP Server. Is an IP entry
really needed ?

https://www.kernel.org/doc/Documentation/frv/booting.txt shows some
examples in specifying ip just by configuring Network via DHCP but it
doesn't say that an ip=:::::dhcp is mandatory  ...

I remember that for some time it just booted normally anyways, so if an
IP entry is required, it's something relatively new.

a2. ZFS is my Root Fileystem. However, first LUKS (cryptsetup/dmcrypt)
needs to be unlucked. And that can happen either by 1) typing the
passphrase in manually or 2) (more desired) having Clevis contacting a
Tang Server during boot to unlock its Keyslots (stored in LUKS).

The order therefore, for automated unlock, is:

Network is UP -> Clevis can contact one of the Tang Servers (I believe
using `curl`) -> Tang provides a key to Clevis -> Clevis unlocks LUKS DM
(Device Mapper) Device -> ZFS imports Pool -> the boot Process continues
as normal

(TLDR: ZFS on top of LUKS, automatically decrypted by Clevis+Tang if
some Tang Servers are up in my LAN)

b. Modified /usr/lib/dhcpcd/dhcpcd-run-hooks with set -x at the top of the 
File, just AFTER the shebang. 
Rebuilt initr with `update-initramfs -k all -u`, `update-grub`, 
`update-initramfs -k all -u` and again `update-grub` to make sure no old stuff 
was hanging around anymore.

Log will be provided shortly ...

c. The scripts were listed in the original post ... including those in /etc 
(none, hence not listed).
But anyhow here you have it:
```
root@MYHOST:~# find {/etc/initramfs-tools,/usr/share/initramfs-tools}/scripts ! 
-type d | sort
/usr/share/initramfs-tools/scripts/functions
/usr/share/initramfs-tools/scripts/init-bottom/lvm2
/usr/share/initramfs-tools/scripts/init-bottom/plymouth
/usr/share/initramfs-tools/scripts/init-bottom/udev
/usr/share/initramfs-tools/scripts/init-premount/brltty
/usr/share/initramfs-tools/scripts/init-premount/plymouth
/usr/share/initramfs-tools/scripts/init-top/all_generic_ide
/usr/share/initramfs-tools/scripts/init-top/blacklist
/usr/share/initramfs-tools/scripts/init-top/brltty
/usr/share/initramfs-tools/scripts/init-top/console_setup
/usr/share/initramfs-tools/scripts/init-top/framebuffer
/usr/share/initramfs-tools/scripts/init-top/udev
/usr/share/initramfs-tools/scripts/local
/usr/share/initramfs-tools/scripts/local-block/cryptroot
/usr/share/initramfs-tools/scripts/local-bottom/clevis
/usr/share/initramfs-tools/scripts/local-bottom/cryptgnupg-sc
/usr/share/initramfs-tools/scripts/local-bottom/cryptopensc
/usr/share/initramfs-tools/scripts/local-bottom/cryptroot
/usr/share/initramfs-tools/scripts/local-bottom/ntfs_3g
/usr/share/initramfs-tools/scripts/local-premount/fixrtc
/usr/share/initramfs-tools/scripts/local-premount/ntfs_3g
/usr/share/initramfs-tools/scripts/local-premount/resume
/usr/share/initramfs-tools/scripts/local-top/clevis
/usr/share/initramfs-tools/scripts/local-top/cryptopensc
/usr/share/initramfs-tools/scripts/local-top/cryptroot
/usr/share/initramfs-tools/scripts/local-top/zfs
/usr/share/initramfs-tools/scripts/nfs
/usr/share/initramfs-tools/scripts/panic/console_setup
/usr/share/initramfs-tools/scripts/panic/plymouth
/usr/share/initramfs-tools/scripts/zfs

```

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064926

Title:
  dhcpcd stuck for 5 Minutes (300 Seconds) during Boot Process
  (LUKS/Clevis Autounlock)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to