Bug 252395

Summary: RHEL 5 network configuration lost when moving removable drives
Product: Red Hat Enterprise Linux 5 Reporter: Isaac W. <ibwilsonvt92>
Component: kudzuAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5.0CC: rvokal
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: 2008-05-05 16:09:47 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:

Description Isaac W. 2007-08-15 19:20:20 UTC
Description of problem:
The network configuration is lost when a removable hard drive with RHEL 5 is 
moved from one computer to another.  Both computers are the same brand and 
model and are equipped with the same hardware.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install the RHEL 5 hard drive in computer #1.
2. Configure the Ethernet device with a static IP address.
3. Reboot computer #1 and note that the network configuration is maintained.
4. Remove hard drive and install in computer #2.
  
Actual results:
At boot, computer hangs with the message "Obtaining IP information" and later 
fails to start the network interface.

Expected results:
At worst, expect Kudzu to come up and ask to migrate the network 
configuration.  At best, expect all network settings to be maintained.

Additional info:

The original ifcfg-eth0 file looks like this:
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.5.10.255
IPADDR=192.5.10.1
NETMASK=255.255.255.0
NETWORK=192.5.10.0
USERCTL=no
ONBOOT=yes
TYPE=Ethernet

When the computer finally comes up, the ifcfg-eth0 file has been changed to 
this:
# Intel Corporation 8255xER/82551IT Fast Ethernet Controller
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=dhcp
HWADDR=00:20:ce:81:1b:50

Comment 3 Bill Nottingham 2008-05-05 16:09:47 UTC
This is changed in the upcoming RHEL 5.2 updates; the network configuration will
not be changed if there is no HWADDR in the config file.

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