Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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.

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

Closing as a duplicate to #2135787

*** This bug has been marked as a duplicate of bug 2135787 ***