This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 455578 - Network is broken after upgrade from RHEL4U6
Network is broken after upgrade from RHEL4U6
Status: CLOSED INSUFFICIENT_DATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.7
i386 Linux
low Severity high
: rc
: ---
Assigned To: Neil Horman
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-16 07:45 EDT by Nicole Dai
Modified: 2010-07-13 11:05 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-13 11:05:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
log information when manually run ifup or server network restart (2.96 KB, text/plain)
2008-07-16 07:45 EDT, Nicole Dai
no flags Details
lspci output (1.96 KB, text/plain)
2008-07-16 22:28 EDT, Nicole Dai
no flags Details

  None (edit)
Description Nicole Dai 2008-07-16 07:45:17 EDT
Description of problem:
After upgrade from RHEL4U6 to RHEL4U7-20080711.0, network cannot be up with the
following outputs:
[root@localhost ~]# ifup eth0

Determining IP information for eth0...SIOCSIFFLAGS: Device or resource busy
SIOCSIFFLAGS: Device or resource busy

Version-Release number of selected component (if applicable):
initscripts-7.93.33-1.el4

How reproducible:
Always

Steps to Reproduce:
1. Fresh install RHEL4U6 (default or everything)
2. Upgrade the RHEL4U6 to RHEL4U7-20080711.0
3. Log on system and ifconfig 
  
Actual results:
No IP address was assigned to the default NIC. ifup or server network restart
outputted the error:
Determining IP information for eth0...SIOCSIFFLAGS: Device or resource busy
SIOCSIFFLAGS: Device or resource busy

Expected results:


Additional info:
Got the following information from /var/log/messages which showed the NIC was up
during the startup:
Jul 16 17:48:29 dhcp-65-148 ifup:
Jul 16 17:48:29 dhcp-65-148 ifup: Determining IP information for eth0...
Jul 16 17:48:29 dhcp-65-148 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 8
Jul 16 17:48:29 dhcp-65-148 dhclient: DHCPOFFER from 10.66.65.254 <30>Jul 16
17:48:29 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 16 17:48:29 dhcp-65-148 dhclient: DHCPACK from 10.66.65.254
Jul 16 17:48:29 dhcp-65-148 NET: /sbin/dhclient-script : updated /etc/resolv.conf
Jul 16 17:48:29 dhcp-65-148 dhclient: bound to 10.66.65.148 -- renewal in 12112
seconds.
Jul 16 17:48:29 dhcp-65-148 ifup:  done.
Jul 16 17:48:29 dhcp-65-148 network: Bringing up interface eth0:  succeeded
Comment 1 Nicole Dai 2008-07-16 07:45:18 EDT
Created attachment 311942 [details]
log information when manually run ifup or server network restart
Comment 2 Bill Nottingham 2008-07-16 13:29:11 EDT
Can you attach the output of lspci? This sounds like a driver issue.
Comment 3 Nicole Dai 2008-07-16 22:28:16 EDT
Created attachment 312007 [details]
lspci output
Comment 4 Neil Horman 2009-12-21 08:39:19 EST
It sounds to me like perhaps something actually started working correctly,  in that, after the upgrade, perhaps NetworkManager is automating the bringup of the interface in question, making the ifup which you issue redundant?
Comment 5 Neil Horman 2010-06-23 14:37:12 EDT
ping any update here?

Note You need to log in before you can comment on or make changes to this bug.