[15:34] <manuvakery1_> Hi. when cloud-init local stage run it is not able to read the network interfaces as the file is not present in /sys/class/net/  and the cloud-init-local service fails to start. Its happening on fedora instance deployed as baremetal on Openstack Ironic. If i add timeout( say 2sec) https://github.com/canonical/cloud-init/blob/b3e31ba228d32c318872fb68edda272f679e1004/cloudinit/net/__init__.py#L354  everything falls in place.  
[15:34] <manuvakery1_> How can i find a fix or a workaround
[15:34] <manuvakery1_> holmanb: this is what i could findout so far
[15:35] <manuvakery1_> I am facing this issue only with fedora,  all other linux distribution works well on the same hardware
[15:37] <holmanb> manuvakery1_: interesting, the sounds to me like we have a race condition that works 'by accident' for all other distros
[15:38] <holmanb> manuvakery1_: sounds like something may have changed causing the interface driver to load slower
[15:41] <manuvakery1_> holmanb: thats what I am thinking but so far no clue what is causing the interface driver to load slower
[15:52] <holmanb> manuvakery1_: which version(s) of Ubuntu did you test on?
[15:53] <manuvakery1_> i have tested Ubuntu18,20 centos7,8 debian9 
[16:06] <holmanb> Different kmod version? Different kernel build defaults? cloud-init gets to this stage faster on fedora for some reason? There are plenty of potential causes. More details would be required to find the cause imo.
[16:12] <manuvakery1_> hmm. I will see the logs more and see if I can find more. I shall provide more details by tomorrow
[16:28] <holmanb> manuvakery1_: something might be amiss with udev/hotplug, but I haven't worked enough with that part of the cloud-init code to know whether that would be a distro issue or a cloud-init issue