Hide Forgot
Description of problem: When a network command in a kickstart file includes --mtu, no MTU value is written to the installed system's ifcfg file in /etc/sysconfig/network-scripts. How reproducible: 100%. Steps to Reproduce: 1. Create a kickstart file with a line like "network --device=eth1 --mtu=8192". 2. Install a new system using this kickstart file. 3. Examine /etc/sysconfig/network-scripts/ifcfg-eth1 on new system. Actual results: There is no MTU= line in the file ifcfg-eth1. Expected results: The file should contain the line "MTU=8192". Additional info: The problem appears to be in kickstart.NetworkData's execute method; the logic there transfers various other settings from the kickstart data object to the Anaconda network device object, but not MTU. I have a patch which I've deployed via an updates.img in my environment (though I'm not certain which branch I should port this patch to for upstream inclusion).
See also: https://github.com/icomfort/anaconda/tree/rhel6-fix-mtu
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
With anaconda-13.21.126 MTU is set to specified value.
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1565.html