Recently I came with an issue, with configuring network using nmconnection files, in combination with loading rootfs remotely.
What I’m doing is that I have an small ISO image, with just the ramdisk, and I load rootfs from network. My kernel arguments look similar to: /proc/cmdline: BOOT_IMAGE=/images/pxeboot/vmlinuz initrd=/images/pxeboot/initrd.img,/images/ignition_ramdisk ignition.firstboot ignition.platform.id=metal ignition.config.url=http://192.168.112.199/ignition_config coreos.live.rootfs_url=http://192.168.112.199/rootfs.img
See that in initrd, I load two ramdisks.
The second ramdisk simply injects a file into /etc/NetworkManager/system-connections/eno1.nmconnection . I can see that file being copied, before the rootfs is loaded
When rootfs starts to be copied, I enter into that directory and see that the i injected into /etc/NetworkManager/system-connections has been removed. As a consequence it doesn’t propagate my network configuration.
So I wanted to raise the issue, looks as a bug to me. Has any one else hit this issue, or is able to reproduce it? What could be the workarounds?