-
Notifications
You must be signed in to change notification settings - Fork 59
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
static IP configured via NM keyfile is not respected on first boot #358
Comments
I'm experiencing the same issue. I'm inserting an ignition file via pxe to configure an install. Ignition successfully installs fedora core but it grabs an IP from DHCP on first boot. When I do a |
Yes. Or NM in the initrd. |
Is this going to be fixed? |
We're working on this in coreos/ignition-dracut#159. |
We are now using NetworkManager in the initramfs and also propagating network information from the initramfs (kargs) when appropriate, which we think fixes this issue. See #394 (comment) and the preceding discussion for more details. |
@miabbott @dustymabe did the fix for this land in 4.4 boot images? |
No, RHCOS 4.4 only special cases ifcfg files right now, see coreos/ignition-dracut#89 |
coreos/fedora-coreos-tracker#358 is fixed now so we shouldn't need a whole section devoted to troubleshooting the issue.
coreos/fedora-coreos-tracker#358 is fixed now so we shouldn't need a whole section devoted to troubleshooting the issue.
…on (#111) * pages/static-ip-config: move around useful information Move the persistent NIC naming and the link to NetworkManager documentation to more appropriate places higher up in the text. * pages/static-ip-config: remove reference to bug 358 coreos/fedora-coreos-tracker#358 is fixed now so we shouldn't need a whole section devoted to troubleshooting the issue. * pages/static-ip-config: Remove note about initramfs network bringup We no longer bring up the network in the initramfs if it's not needed. See coreos/fedora-coreos-tracker#443.
I was testing the NM keyfile in the docs PR (coreos/fedora-coreos-docs#30) and found that the static IP was not respected on first boot.
The keyfile was correctly landed via Igntion as such:
But the
eth0
interface did not come up with the static IP, rather it came up with a DHCP assigned address.I was able to force it to use the static IP after using
nmcli connection down eth0
Additionally, on subsequent boots, the static IP does come up correctly.
This feels like another case where bringing down the networking in the initrd would solve the issue (re: #356 (comment))
The text was updated successfully, but these errors were encountered: