Skip to content

fix(netboot): keep EL10 diskless nodes from DHCP on every port - #8008

Open
viniciusferrao wants to merge 4 commits into
xcat2:masterfrom
VersatusHPC:fix/el10-netboot-auto-default
Open

viniciusferrao wants to merge 4 commits into
xcat2:masterfrom
VersatusHPC:fix/el10-netboot-auto-default

Conversation

@viniciusferrao

Copy link
Copy Markdown
Member

NetworkManager in an EL10 diskless image makes a DHCP profile for every Ethernet port without one. A port with a link but no DHCP server keeps NetworkManager-wait-online from finishing, so the node boots degraded. Diskful nodes are not affected, because anaconda writes a profile for every port.

genimage now sets no-auto-default=* in the NetworkManager configuration of EL10 images. The boot interface keeps the profile from the initial ramdisk.

The interfaces that otherifce names got DHCP only from those automatic profiles, because EL10 reads no ifcfg files. genimage now writes NetworkManager keyfiles for them on EL10, and a rebuild replaces them.

Thanks-to: SpacemiT (riscv64 test hardware)

genimage wrote an ifcfg file for each interface that otherifce or
genimage -r names. EL10 reads no ifcfg files, and its images have no
network-scripts directory. Such an interface got DHCP only from the
profile that NetworkManager makes for any port without one.

genimage now writes a NetworkManager keyfile with DHCP for each of these
interfaces on EL10 and later. A rebuild replaces the keyfiles of the
earlier build. Older releases still get the same ifcfg files.
An EL10 image must get a DHCP keyfile for each requested interface,
also when it has a network-scripts directory. Only root can read the
keyfiles, and the interface of the initial ramdisk gets none. A rebuild
must drop the keyfile of an interface that is no longer requested and
keep other profiles. An EL9 image must keep its ifcfg files.
NetworkManager in an EL10 diskless image made a DHCP profile for every
Ethernet port without one. A port with a link but no DHCP server kept
NetworkManager-wait-online from finishing, so the node booted degraded.
Diskful nodes are not affected, because anaconda writes a profile for
every port.

genimage now sets no-auto-default=* in the NetworkManager configuration
of EL10 images. The boot interface keeps the profile from the initial
ramdisk. The other interfaces get only the profiles that the image or
the xCAT network configuration gives them.
An EL10 image must turn off the automatic DHCP profiles. An EL9 image
must keep the NetworkManager defaults, and an image without
NetworkManager must get no NetworkManager configuration.
@viniciusferrao
viniciusferrao requested a review from dhilst October 30, 2026 21:47
@viniciusferrao viniciusferrao self-assigned this Oct 30, 2026
@viniciusferrao viniciusferrao added this to the 2.20 milestone Oct 30, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant