This bug was fixed in the package dhcpcd - 1:10.0.6-1ubuntu3.1
---
dhcpcd (1:10.0.6-1ubuntu3.1) noble; urgency=medium
* hooks/30-hostname: Exit with 0 if setting hostname is not needed
This prevents retrying dhcpcd for 5 minutes during boot. (LP: #2064926)
-- Benjamin Drung
This bug was fixed in the package initramfs-tools - 0.142ubuntu27
---
initramfs-tools (0.142ubuntu27) oracular; urgency=medium
* Run wrap-and-sort
* initramfs-tools-core: drop support for upgrading from < 0.138
* Convert debian/copyright to machine-readable format
* Switch to
This bug was fixed in the package dhcpcd - 1:10.0.6-4
---
dhcpcd (1:10.0.6-4) unstable; urgency=medium
[ Benjamin Drung ]
* [ patches ]
+ hooks/30-hostname:
Exit with 0 if setting hostname is not needed (LP: #2064926).
-- Martin-Éric Racine Tue, 07 May 2024
13:49:47
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
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
** Attachment added: "initramfs_proposed_testing.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5776985/+files/initramfs_proposed_testing.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hello Timo.
Sure, I just tested it and I get to the (same) Result I was getting
while performing preliminary Investigations. The boot time is around 22
Seconds (down from the Original 300 Seconds).
So it's Good, from what I can tell :).
# Test Procedure & Log
# Pin noble-proposed Packages with
** Attachment added: "dmesg_proposed_testing.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5776984/+files/dmesg_proposed_testing.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Hello Stefano, or anyone else affected,
Accepted dhcpcd into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dhcpcd/1:10.0.6-1ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Yes, I edited the bug description to add the SRU bug sections. There is
no automation for that.
--
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)
Just for my understanding (I had a look at that Wiki Page but didn't
understand very well) ... Did you create a SRU Bug Template ? I only see
a Patch here and the Upstream Bug Reports.
Is the SRU Bug Template creation part an automatic Pipeline ran by a Bot
?
--
You received this bug notificatio
** Tags added: patch
--
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 abo
mantic and before are not worth the backport, but noble is a LTS
release.
Once the SRU team accepts the upload, it will land in noble-proposed and
you will get asked to test the fix. See
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member o
Pretty sure the same/similar occurs in Mantic and probably even before
(even if I believe dhcpcd version is different).
But maybe it's too much effort for little benefit to fix those (Mantic
will be anyways EOL July 2024 so just a few months away). I had upgraded
all Systems that I own to Ubuntu 2
Debdiff for noble
** Description changed:
+ [ Impact ]
+
+ Systems that use clevis will have a 5 minutes boot delay, because dhcpcd
+ fails and retries until the retry loop exits.
+
+ [ Test Plan ]
+
+ Use a system with clevis and zfs where /etc/hostname is set and differs
+ from the hostname
We can include the fix in Ubuntu 24.04 via a stable release update.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Also affects: dhcpcd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Noble)
Importance: Undecided
Super, many thanks. But I'll basically have to "patch" it locally,
because I guess this will not make it to Ubuntu before 24.10 at best,
right ?
New BUG Report at (hope I did it correctly):
https://bugs.launchpad.net/ubuntu/+source/dhcpcd/+bug/2065037
EDIT 1: I accidentally assigned it to initram
Suggested title for the second bug: dhcpcd is called before interfaces
have carrier causing a 29 seconds boot delay
The bug title and description can be updated afterwards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Forwarded fix upstream: https://github.com/NetworkConfiguration/dhcpcd/pull/320
and to Debian: https://salsa.debian.org/debian/dhcpcd/-/merge_requests/6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
Alright.
Can you please tell me what I should report in the other bug exactly
though ?
My original idea in the first post ?
>>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 R
The Launchpad UI only allows to attach one file at once. So that is
normal.
I'll prepare the upload containing the fix. That your boot takes around
45 seconds instead of 15 seconds is caused by a separate issue. Please
file another bug for that. Here is the relevant log:
```
dhcpcd-10.0.6 startin
** Attachment added: "dmesg_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775772/+files/dmesg_v4.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
It seems, looking at `dmesg` at least, that the "frozen" / "hang" state
went from 300 Seconds to 45 Seconds.
PS: is it normal that I cannot attach multiple files at once ?
** Attachment added: "initramfs_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachm
Yes, I can confirm. Without a precise clock but just counting in my
head, it's around 45 seconds. Definitively much less than before.
Maybe I'll try to quickly play with PXE Boot / TFTP Server settings on
my OPNSense Router and see if that's responsible for the slowdown
(dhcpcd reported those PXEL
Sure, I can change it.
I'll do the change and reboot ... We'll have an answer in about 30
Minutes.
Another thing that I was thinking about is ... The `/etc/hostname` of
the System is `ubuntuworkstation01` and the DHCP-assigned (or should I
say "registered" ?) hostname is apparently `WORKSTATION01
If I understand the code correctly, 30-hostname only changes the
hostname if it was the default like `(none)` or if it was set by dhcpcd
previously (that's why need_hostname checks for the old hostname).
In case /etc/hostname is included in the initrd (which is probably the
case for your initrd),
Looking for reason environment variable in initramfs_v3.debug, we have
following result: reason=PREINIT, reason=NOCARRIER, and reason=CARRIER
have no problems.
reason=BOUND and reason=REBOOT show the failure. environment variables
there:
```
hostname_fqdn=no
if_configured=true
if_down=false
if_up
Seems like only PATH and PWD are set ...
EDIT: correction, these variables are set (I ignored the lowercase ones because
I expected everything in ENV to be uppercase):
```
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin
PWD=/
hostname_fqdn=no
if_configured=true
if_down=false
if_up=false
ifcarri
Updated /run/initramfs/initramfs.debug with env | sort (and also set -x
immediately afterwards) in dhcpcd Script (v3)
** Attachment added: "initramfs_v3.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775624/+files/initramfs_v3.debug
--
You received
** Attachment added: "initramfs_v3.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775623/+files/initramfs_v3.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
No additional "set -x" is needed there since that file is sourced and
therefore your initial "set -x" is still set.
This bug does not look like being related to netplan at all. initramfs-
tools generates configs for netplan, but this is unrelated to the dhcpcd
hooks.
--
You received this bug not
Could it be related to the fact that I completely uninstalled `netplan`
from my Ubuntu Desktop ?
I saw lots of References to Netplan in `/usr/share/initramfs-
tools/scripts/functions`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Sure. Do I also need to add set -x there as well ?
--
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
Can you add a call to `env | sort` at the beginning of
/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname to log what environment
variables are set?
--
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:
It's a bug in /usr/lib/dhcpcd/dhcpcd-hooks/30-hostname when executed
with "set -e" that nobody has noticed/reported in 1.5 years.
If I understand correctly, need_hostname returns 0 in case the hostname
is already set to the correct name. It return 1 if the hostname needs to
be set. "need_hostname
Scratch my last comment. My test should have called `busybox sh test`
instead of `busybox test`.
The failing code is a bit later. need_hostname hits the last else part
and calls false (after the "No old hostname" comment). The caller code
in set_hostname:
```
need_hostname || return
```
No worries, you are super quick to reply, I appreciate that a lot.
But ... What does this mean ? Is it a BUG that lingered around for 1.5
years without anybody else reporting it ?
Or is it a (mis)configuration Issue somewhere on my side ?
--
You received this bug notification because you are a
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/
I had uploaded it ... it's approximately 300 more lines than before.
--
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
Thanks. So clevis-initramfs (from the clavis source package) ships
/usr/share/initramfs-tools/scripts/local-top/clevis which calls
configure_networking. As you described configuring the network is
desired. So clevis and initramfs-tools behave as expected and the bug is
inside dhcpcd. Let's see what
Updated /run/initramfs/initramfs.debug with set -x in dhcpcd Script
** Attachment added: "Updated /run/initramfs/initramfs.debug with set -x in
dhcpcd Script"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775551/+files/initramfs_v2.debug
--
You received
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 conf
What scripts do you have on your system?
```
find {/etc/initramfs-tools,/usr/share/initramfs-tools}/scripts ! -type d | sort
```
--
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The first question is: Why is the network configured in
the initrd in the first place? Your dmesg says that the ZFS is used to
boot and no "ip" parameter is specified there.
The second question is: Why did /usr/lib
Also adding DMESG Output immediately after Boot Process finishes.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775478/+files/dmesg.debug
** Tags added: cryptsetup
--
You received this bug notification because you are a memb
44 matches
Mail list logo
