Hey there,

For those of you who use Fedora often on public cloud providers where cloud-init handles the initial configuration, there's a change coming for the very early DHCP request during the boot. ☁️

As reported in BZ 2247055[0], the existing dhclient binary comes from ISC's dhcp and it stopped being maintained upstream in 2022. Cloud-init uses dhclient during the very early setup process to get an IP address for retrieving instance metadata.

Busybox provides udhcpc[1] and it works well for cloud-init's early boot needs. Support for udhcpc was also added to cloud-init.

I've tested this on AWS and it's working well. You shouldn't notice a difference when launching a cloud instance after this change, but I wanted to ensure everyone was aware it was coming. 😉

Have a great rest of the week!

[0] https://bugzilla.redhat.com/show_bug.cgi?id=2247055
[1] https://en.wikipedia.org/wiki/Udhcpc

--
Major Hayden
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to