Fedora 35/36/37 cloud-init does ignore network-config settings for nameservers (patch for v2)

[Mandragor]

I have an environment, where i need to provide the nameservers and do not get the "right" ones from dhcp.
While ubuntu cloud image has no problems to parse the nameserver entry, fedora cloud image ignores the nameserver setting in cloud-init v1.

After reading the code in proxmox, i foud a nearly completed implementation for cloud-init v2 - or at least for the v2 network configuration.

I have added a nocloud2 for the citype - with this the v2 section of network-conf is generated --> WORKS for fedora cloudinit 35/36/37!

Can you apply this or a similar patch to support nocloud2 option for citype? Would be really helpful!


I used the following image (you need to decompress and import it
https://ftp.halifax.rwth-aachen.de/.../images/Fedora-Cloud-Base-37-1.7.x86_64.qcow2

 

[mira]

We may be able to switch to it starting with PVE 8 since nowadays all current distributions, including RHEL, have cloud-init versions that support it.

I've opened an enhancement request in our bugtracker to keep track of it: https://bugzilla.proxmox.com/show_bug.cgi?id=4469

If we plan on making it opt-in until then, I'll update the enhancement request.

For patches please use the pve-devel list [0] and check out our Developer Documentation wiki entry [1].


[0] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[1] https://pve.proxmox.com/wiki/Developer_Documentation

 

[unixsh]

Hi there !

I've spent many days by trying to understand why my fedora template wasn't setting the nameserver via cloudinit deployment, and I finally found the answer in this thread.

First, many thank's @Mandragor for your patch, that's now working, I really appreciate !
But now what about integrating this change into current PVE version @mira ? This thread is almost one year ago, I'm currently using 8.0.4, and this improvement would be really appreciated.

Thank's

 

[return true;]

Was there any traction on a supported resolve for this? Seems to still be an issue as of 8.1.4 and Fedora Cloud 39.