Bug 2019813

Summary:	Kickstart network --mtu option is ignored
Product:	Red Hat Enterprise Linux 9	Reporter:	Radek Vykydal <rvykydal>
Component:	anaconda	Assignee:	Radek Vykydal <rvykydal>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	bstinson, jkonecny, jstodola, jwboyer, linux, release-test-team-automation, rvykydal
Target Milestone:	rc	Keywords:	Triaged
Target Release:	9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-34.25.0.20-1.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	2018301	Environment:
Last Closed:	2022-05-17 12:30:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2018301
Bug Blocks:

Description Radek Vykydal 2021-11-03 11:59:56 UTC

+++ 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

Comment 1 Radek Vykydal 2021-11-03 12:02:13 UTC

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.

Comment 3 Radek Vykydal 2021-11-05 12:56:51 UTC

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

Comment 4 Jan Stodola 2021-11-18 15:45:23 UTC

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.

Comment 7 Jan Stodola 2021-11-22 09:06:47 UTC

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

Comment 9 errata-xmlrpc 2022-05-17 12:30:45 UTC

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