Bug 154726

Summary: pump does not set MTU when setting up a device
Product: Red Hat Enterprise Linux 3 Reporter: Sean Dilda <agrajag>
Component: pumpAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-24 18:03:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch to cause pump to set the mtu
none
Updated patch none

Description Sean Dilda 2005-04-13 20:07:44 UTC 
If the flags are set for pump to change the MTU on a device, it ignores those flags.

The following patch will cause the MTU to be set when pumpSetupInterface is called.

This is required for an MTU= setting in /tmp/netinfo to take effect during an
install.
Comment 1 Sean Dilda 2005-04-13 20:07:45 UTC 
Created attachment 113114 [details]
Patch to cause pump to set the mtu
Comment 2 Sean Dilda 2005-04-14 19:13:53 UTC 
Created attachment 113179 [details]
Updated patch

This patch also allows pump to grab the MTU from the dhcp server (but only if
the dhcp server is configured to send this information).  It also includes the
previous patch that allows pump to set the MTU.

In theory these combined changes will allow anaconda to get the MTU from the
dhcp server at install time without the admin having to specify it in any other
way.
Comment 3 Jeremy Katz 2005-04-20 16:04:58 UTC 
Committed to HEAD for pump 0.8.22.  Should also make its way into RHEL3 U6 and
RHEL4 U2 based on a related feature request.
Comment 4 Jeremy Katz 2006-04-24 18:03:41 UTC 
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed).  If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.