RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

+++ This bug was initially created as a clone of Bug #2018301 +++

I set up several network interfaces in a kickstart file, including like this:

network --device=eno3 --mtu=9000 --bootproto=static --ip=10.0.8.5 --netmask=255.255.255.0 --noipv6 --activate

Everything was set except for the MTU - it was not set during install or on the installed system (no MTU= line at all in ifcfg files).

--- Additional comment from Radek Vykydal on 2021-11-02 15:03:10 UTC ---

Could you please attach log file /var/log/anaconda/journal.log from the installed system?

--- Additional comment from Chris Adams on 2021-11-03 00:37:54 UTC ---

One thing I didn't think but could matter - this kickstart sets the network config in a %pre script that's then %included.

--- Additional comment from Radek Vykydal on 2021-11-03 11:47:10 UTC ---

Upstream PR with fix:
https://github.com/rhinstaller/anaconda/pull/3678

--- Additional comment from Radek Vykydal on 2021-11-03 11:50:33 UTC ---

Reproduced locally using this kickstart:

%include /tmp/ksinclude
%pre
echo "network --device=ens3 --bootproto=dhcp --mtu=9000" > /tmp/ksinclude
%end

--- Additional comment from Radek Vykydal on 2021-11-03 11:54:20 UTC ---

PR for a kickstart test update: https://github.com/rhinstaller/kickstart-tests/pull/613

On RHEL 9 kickstart network command is always applied in Anaconda (in RHEL 8 it is only for commands included via %include) so it is actually a regression from RHEL 8.

https://github.com/rhinstaller/anaconda/pull/3686

Reproduced on RHEL-9-Beta using the "network-options-pre" kickstart-test:
*** Failed check: MTU=9000 in /etc/sysconfig/network-scripts/ifcfg-enp3s0 or ethernet.mtu=9000 in /etc/NetworkManager/system-connections/enp3s0.nmconnection

The same test passed on RHEL-9.0.0-20211117.d.7 with anaconda-34.25.0.20-1.el9:
INFO: RESULT:network-options-pre:9e5f6e755cbb:SUCCESS:test done

Marking the bug as Verified:Tested.

anaconda-34.25.0.20-1.el9 is included in RHEL-9.0.0-20211121.7, moving to VERIFIED.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: anaconda), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2326