Project

General

Profile

Actions

Bug #37367

closed

Foreman and Anaconda are not in sync when deploying RHEL9: both keyfiles/snippets and ifcfg-xxx files are generated

Added by Shimon Shtein 14 days ago. Updated 13 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

RHEL9 installed from Foreman 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
total 12
-rw------
. 1 root root 425 Oct 10 12:18 bond0.nmconnection
rw------. 1 root root 282 Oct 10 12:18 ens3f0.nmconnection
rw------. 1 root root 282 Oct 10 12:18 ens3f1.nmconnection
[root@ ~]# ls ll /etc/sysconfig/network-scripts/
total 12
-rw-r--r-
. 1 root root 309 Oct 10 12:19 ifcfg-bond0
rw-r--r-. 1 root root 129 Oct 10 12:19 ifcfg-ens3f0
rw-r--r-. 1 root root 129 Oct 10 12:19 ifcfg-ens3f1
~~

Example simple Virtual Machine (Vmware):
~~
[root@ ~]# ls ll /etc/NetworkManager/system-connections
total 4
-rw------
. 1 root root 417 Oct 10 12:54 ens192.nmconnection
[root@ ~]# ls ll /etc/sysconfig/network-scripts/
total 4
-rw-r--r-
. 1 root root 252 Oct 10 12:55 ifcfg-ens192
~~

This makes managing systems very confusing as keyfiles by default will be prioritized.

Foreman should support keyfiles when installing RHEL9 or only use ifcfg files (if supported by anaconda)

Actions #1

Updated by The Foreman Bot 14 days ago

  • Status changed from New to Ready For Testing
  • Assignee set to Shimon Shtein
  • Pull request https://github.com/theforeman/foreman/pull/9961 added
Actions #2

Updated by The Foreman Bot 13 days ago

  • Fixed in Releases 3.11.0 added
Actions #3

Updated by Shimon Shtein 13 days ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF