Bug #37364
open[RFE] Satellite and Anaconda are not in sync when deploying RHEL9: both keyfiles/snippets and ifcfg-xxx files are generated
Description
Satellite doesn't support keyfiles when provisioning RHEL9: it creates ifcfg during provisioning.
RHEL9 installed from Satellite are thus creating duplicated and confusing files
tl;dr: It seems Anaconda creates the keyfiles/snippets used by RHEL9 and at the same time Kickstart from Satellite is creating ifcfg files duplicating the configuration!
Example of a Physical Machine with bond:
~~
[root@ ~]# ls ll /etc/NetworkManager/system-connections. 1 root root 425 Oct 10 12:18 bond0.nmconnection
total 12
-rw------rw------. 1 root root 282 Oct 10 12:18 ens3f0.nmconnectionrw------. 1 root root 282 Oct 10 12:18 ens3f1.nmconnection
[root@ ~]# ls ll /etc/sysconfig/network-scripts/. 1 root root 309 Oct 10 12:19 ifcfg-bond0
total 12
-rw-r--r-rw-r--r-. 1 root root 129 Oct 10 12:19 ifcfg-ens3f0rw-r--r-. 1 root root 129 Oct 10 12:19 ifcfg-ens3f1
~~
Example simple Virtual Machine (Vmware):
~~
[root@ ~]# ls ll /etc/NetworkManager/system-connections. 1 root root 417 Oct 10 12:54 ens192.nmconnection
total 4
-rw------
[root@ ~]# ls ll /etc/sysconfig/network-scripts/. 1 root root 252 Oct 10 12:55 ifcfg-ens192
total 4
-rw-r--r-
~~
This makes managing systems very confusing as keyfiles by default will be prioritized.
What we would expect is that Foreman fully supports keyfiles or at least support both installation methods (ifcfg-xxx and keyfiles)
No data to display