Dracut `ifname=` kernel argument for NIC naming is not propagated to the installed system for Single Node OpenShift (SNO)

Solution Verified - Updated -

Issue

  • When booting the Single Node OpenShift (SNO) installer, a user provides kernel arguments to assign a predictable network interface name using ifname=<interface>:<MAC> and then uses the ip= parameter to assign a static IP address or bond to that new interface name.
  • For example, the user provides the following kernel arguments to name an interface myens1 based on its MAC address, and then configure it:
    ifname=myens1:00:1A:4A:16:01:5A ip=192.168.100.10::192.168.100.1:255.255.255.0:sno.example.com:myens1:none
  • In the live installer environment, the ifname parameter successfully renames the interface, and the ip= parameter configures it correctly, allowing the SNO installation to proceed.
  • However, after the installation completes and the node reboots into the final Red Hat CoreOS (RHCOS) system, the custom interface name assigned by the ifname argument is not persisted.
  • The network interface reverts to its original kernel-assigned name (e.g., ens1f0), and the static IP or bond configuration, which was targeted at the custom name (myens1), is not applied. This can leave the SNO node inaccessible on the network.

Environment

  • Red Hat OpenShift Container Platform (OCP)
    • 4.14 and newer
  • Single Node OpenShift (SNO)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content