EL 9 using /etc/NetworkManager/system-connections/ as default but Foreman template doesn't support

Support
,
1

I have built a physical machine with EL9 and network bonding enabled but after first reboot server went out of Network and ip has been lost .When i ran below commands network got configured properly

rm -rf /etc/NetworkManager/system-connections/*
nmcli connection migrate
systemctl restart NetworkManager

What changes are required in Foreman provisioning template to use new way of Networking which is enabled by reading /etc/NetworkManager/system-connections/ instead of /etc/sysconfig/network-scripts(old way) .Does latest provisioning templates support this ?

2

Unfortunately the templates have not been changed to reflect this upstream change.

To add support for this I would rename kickstart_networking_setup to kickstart_networking_setup_ifcfg. Add a similar snippet as kickstart_networking_setup_networkmanager and a new one as kickstart_networking_setup containing an if-clause taking the kickstart_networking_setup_ifcfg for EL < 9 and Fedora < 36 (?) and the new kickstart_networking_setup_networkmanager as default.

I do not see an issue for this already. So if you can add a template this would be great, if not can you create an issue at Overview - Foreman? Thanks for bringing this up.

1 Like
3

Yeah this is a known issue that we are planning to fix, we already have several issues for it in Bugzilla:

2 Likes
4

In my setup I used static IP during kickstart and I just commented out:

<%= snippet 'kickstart_networking_setup' %>

… and let kickstart persist the NetworkManager config to disk.

Works well.