[Bug 2064926] Re: dhcpcd stuck for 5 Minutes (300 Seconds) during Boot Process (LUKS/Clevis Autounlock)

[Benjamin Drung]

I started writing my comment before you posted your log output. That's
why I saw it only afterwards.

I tracked it down to: /usr/lib/dhcpcd/dhcpcd-run-hooks ->
/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname -> need_hostname function:

```
	is_default_hostname "$hostname" && return 0
```

/usr/lib/dhcpcd/dhcpcd-hooks/10-mtu calls "set -e" which is still
present when sourcing /usr/lib/dhcpcd/dhcpcd-hooks/30-hostname.

Distilled down `test` shell code:

```
#!/bin/sh
set -e

need_hostname()
{
    false && return 0
    echo "remaining"
}

need_hostname
```

busybox behaves differently than dash in that case:

```
$ sh test; echo $?
remaining
0
$ busybox test; echo $?
1
```

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

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

Status in dhcpcd package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This is a long-lingering issue, probably affecting Ubuntu 23.04,
  surely Ubuntu 23.10 and now surely Ubuntu 24.04.

  Due to other Priorities I kept having my PC on Standby/Sleep instead
  of turning it off all the time, since I would incur in 5 Minutes (300
  Seconds) Boot being frozen.

  I also thought it was due to Clevis LUKS Autounlock at first:
  https://github.com/latchset/clevis/issues/289#issuecomment-1322633750

  But according to the messages I see on the Screen during boot (if I
  see them !), it seems this is purely a dhcpcd Issue.

  On one workstation the Screen is completely frozen, but boot Process
  continues normally after 5 Minutes have elapsed.

  This BUG Report is based on the Machine that shows *some* Output while
  being Stuck.

  Looks Similar to this one, but I do NOT have aoetools installed
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2062501

  List of Initramfs Scripts Installed in the system:

  /usr/share/initramfs-tools/scripts/init-bottom/udev
  /usr/share/initramfs-tools/scripts/init-bottom/lvm2
  /usr/share/initramfs-tools/scripts/init-bottom/plymouth
  /usr/share/initramfs-tools/scripts/panic/console_setup
  /usr/share/initramfs-tools/scripts/panic/plymouth
  /usr/share/initramfs-tools/scripts/nfs
  /usr/share/initramfs-tools/scripts/functions
  /usr/share/initramfs-tools/scripts/zfs
  /usr/share/initramfs-tools/scripts/init-premount/brltty
  /usr/share/initramfs-tools/scripts/init-premount/plymouth
  /usr/share/initramfs-tools/scripts/local-bottom/cryptgnupg-sc
  /usr/share/initramfs-tools/scripts/local-bottom/ntfs_3g
  /usr/share/initramfs-tools/scripts/local-bottom/clevis
  /usr/share/initramfs-tools/scripts/local-bottom/cryptroot
  /usr/share/initramfs-tools/scripts/local-bottom/cryptopensc
  /usr/share/initramfs-tools/scripts/local-premount/fixrtc
  /usr/share/initramfs-tools/scripts/local-premount/resume
  /usr/share/initramfs-tools/scripts/local-premount/ntfs_3g
  /usr/share/initramfs-tools/scripts/local
  /usr/share/initramfs-tools/scripts/local-block/cryptroot
  /usr/share/initramfs-tools/scripts/local-top/cryptopensc
  /usr/share/initramfs-tools/scripts/local-top/clevis
  /usr/share/initramfs-tools/scripts/local-top/cryptroot
  /usr/share/initramfs-tools/scripts/local-top/zfs
  /usr/share/initramfs-tools/scripts/init-top/all_generic_ide
  /usr/share/initramfs-tools/scripts/init-top/brltty
  /usr/share/initramfs-tools/scripts/init-top/udev
  /usr/share/initramfs-tools/scripts/init-top/framebuffer
  /usr/share/initramfs-tools/scripts/init-top/console_setup
  /usr/share/initramfs-tools/scripts/init-top/blacklist

  A possible workaround would be to manually edit /usr/share/initramfs-tools/scripts/functions
  Changing this: 
  `for ROUNDTTT in 30 60 90 120; do`

  To this:
  `for ROUNDTTT in 15 15 15 15; do`

  However it's really a last resort Workaround.

  Any hope of a proper Fix ?

  Possible mentions based on the logs output: 
  ```
  enp0s25: ignoring offer of 192.168.3.61 from 192.168.1.8
  enp0s25: probing address 192.168.3.61/20
  ```

  This might be due to High-Availability Configured in my OPNSense
  Router. There is a Master (192.168.1.7) and a Slave (192.168.1.8).

  VLAN should be ENABLED, but right now ALL traffic flows on VLAN 1 /
  default VLAN (untagged), so this shouldn't be an issue IMHO. Didn't
  have time to setup VLANs yet.

  Why does dhcpcd exit like this? What is the Error ?
  ```
  script_status: /usr/lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
  ```

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