Hello Major,
I think this is stupid anyway. Why does cloud-init need 2 separate DHCP
clients anyway? Can we gather what exactly they use it for and why
alternative dhcp client is required?
It seems to me NetworkManager should be able to use just different
configuration for "pre-connection" phase. But anyway, it is connected by
that time. Pretending alternative dhcp client makes it "off-line" is
ridiculous. It might not be reaching network.target with it, but still
is connected.
It would be great, if Network Manager could be used in both phases.
Could for example --configure-and-quit with custom --config and
--state-file provide basic configuration needed before correct network
start? Were that even considered?
Regards,
Petr
On 30. 01. 24 17:58, Major Hayden wrote:
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
--
Petr Menšík
Software Engineer, RHEL
Red Hat, http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
