Bug 2162348 - Satellite uses deprecated network configuration file format with RHEL 9
Summary: Satellite uses deprecated network configuration file format with RHEL 9
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.11.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Leos Stejskal
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-19 11:42 UTC by Marko Myllynen
Modified: 2023-07-11 17:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-16775 0 None None None 2023-03-28 04:46:23 UTC
Red Hat Knowledge Base (Solution) 6996643 0 None None None 2023-02-06 01:59:31 UTC

Description Marko Myllynen 2023-01-19 11:42:44 UTC
Description of problem:
RHEL 9 deprecates ifcfg configuration files and uses the ini-style connection files by default:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.0_release_notes/index#deprecated-functionality_networking

However, it seems Satellite 6.11 still creates ifcfg when kickstarting RHEL 9 VMs using Satellite. As ifcfg files are deprecated only new ini-style files should be used and nothing should be created in /etc/sysconfig/network-scripts. Thanks.

Version-Release number of selected component (if applicable):
Satellite 6.11.4

Comment 2 Leos Stejskal 2023-01-31 09:50:41 UTC
Hi, this is know issue, reported also in https://bugzilla.redhat.com/show_bug.cgi?id=2135787 and https://bugzilla.redhat.com/show_bug.cgi?id=2163010.

I suggest to remove the BZ from the 6.13 scope, this issue is there for some time (from RHEL 7),
and implementing correct network configuration in templates which is backwards compatible back to RHEL 6 is just not feasible in the 6.13 scope.

Comment 5 Leos Stejskal 2023-05-29 11:30:48 UTC
Hi,
I propose to remove the BZ from 6.14. Due to other work on other tasks, we didn't manage to fix it in time
and there is a little chance we can make it into the 6.14.

I created a task [0] for the investigation of what needs to be done and what would be the impact,
but I am sure that it's not going to be a small bugfix or a small change.

[0] https://issues.redhat.com/browse/SAT-17931


Note You need to log in before you can comment on or make changes to this bug.