-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FCOS asking for two DHCP leases #58
Comments
There are a couple pieces here:
On the basis of point 1, I'd probably advocate for not changing this behavior. Otherwise, the network setup will happen via a different path only on the first boot. |
Yeah, that's a good point. It'd be neat though if we could let the stack take care of this for us (i.e. NM or dhclient understanding that it's safe to reuse the same connection if the configs match). One side effect of this right now is that e.g. |
If we're actually getting two different IP addresses, that seems like a server misconfiguration? I'd expect a second request from the same MAC to return the existing valid lease. |
I'm seeing this in the local libvirt case. |
Right now in FCOS, VMs are getting *two* IP addresses when testing locally in libvirt. The root of the issue is that the first request in the initrd is using a different client ID than the one from NM in the real root. This throws off at least dnsmasq, which then refuses to give out the same IP again. Tell NM to also use the MAC address as the client ID, to match what `dhclient` also does in the initrd. For more background information, see: coreos/fedora-coreos-config#58 Closes: coreos/fedora-coreos-config#58
Unwilling to let this go, I finally got to the bottom of it! PR in coreos/coreos-assembler#367. |
Right now in FCOS, VMs are getting *two* IP addresses when testing locally in libvirt. The root of the issue is that the first request in the initrd is using a different client ID than the one from NM in the real root. This throws off at least dnsmasq, which then refuses to give out the same IP again. Tell NM to also use the MAC address as the client ID, to match what `dhclient` also does in the initrd. For more background information, see: coreos/fedora-coreos-config#58 Closes: coreos/fedora-coreos-config#58
jenkins/rdgo: Archive rdgo artifacts
Right now, booting FCOS will result in two DHCP leases being handed out: once during the initrd, and once more in the real root. I initially thought this was because unlike in FAH, we weren't shipping
initscripts
, which has a legacy script to copy networking data over from the initrd (though in addition to that, FAH also doesn't set up networking since we don't haverd.neednet=1
).Anyway, I was playing with variations of:
Though for some reason, NetworkManager still calls
dhclient
again. The lease file then ends up with two also identical entries.Interestingly, on RHCOS maipo, this does not happen, even though
rhel-import-state
is disabled, and NetworkManager does end up callingdhclient
again. Though it looks likedhclient
is happy reusing the same lease.The text was updated successfully, but these errors were encountered: