Hi,
I'm not 100 percent confident this is the correct place for this but feel free to
point me to a more appropriate place if there is one.. I'm seeing two separate issues
with the latest version of IoT that I was hoping for some assistance with.
1. During boot if DHCP is unavailable it takes a significant amount of time to boot
waiting for a timeout to occur. This seems to be related to dracut-network and ignition.
The closest thing I could find was a bug report for CoreOS [1] that seemed to be a way to
over ride that behavior but I personally couldn't get it to work. Is there a way to
override this behavior? I have a system where an IPMI interface reports as having a link
but can't get a DHCP address and thus is forced to wait for a timeout.
2. I can't set a static IP address within the OS even though per the docs [2] this
should be possible (as it was on 31 IoT). Basically once you set a static address and boot
there's a new network connection that's activated and utilizing DHCP while the
static one is there unused. I've tried deleting the connection ,recreating it, etc
and it just doesn't seem to stick.
[1]
https://github.com/coreos/ignition-dracut/issues/94
[2]
https://docs.fedoraproject.org/en-US/iot/admin-tasks/