Bug 234075 - Using PERSISTENT_DHCLIENT with no link present
Using PERSISTENT_DHCLIENT with no link present
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-26 17:30 EDT by Paul B Schroeder
Modified: 2014-03-16 23:06 EDT (History)
1 user (show)

See Also:
Fixed In Version: 8.52-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-04-16 18:12:36 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)
ifup-eth CHECK_LINK_DOWN patch (976 bytes, patch)
2007-03-26 17:30 EDT, Paul B Schroeder
no flags Details | Diff

  None (edit)
Description Paul B Schroeder 2007-03-26 17:30:42 EDT
Description of problem:
The machines we have come up significantly faster than the switch which they are
connected to.  Because of this, the network device never gets started.  Setting
PERSISTENT_DHCLIENT=yes solves part of the problem.  The part that is causing a
problem, however, is that ifup-ethX uses the check_link_down() function to
determine if a link is present.  If there is not link present, it exits and
never bothers to start dhclient for the device.  In this case, there is no link
present yet as the switch is still booting.  It would be nice if there were
another option that could be added to ifcfg-ethX which would allow us to shut
off the check_link_down() check.  It would be nice to have in conjunction with
PERSISTENT_DHCLIENT

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


How reproducible:

Steps to Reproduce:
1. Configure eth device to use dhcp
2. Boot machine or restart the network without the network cable plugged in.
3.
  
Actual results:
The network interface and dhclient will not start.

Expected results:


Additional info:
Created a quick, simple patch which essentially checks CHECK_LINK_DOWN to
determine whether or not to execute the check_link_down function.
Setting PERSISTENT_DHCLIENT=yes and CHECK_LINK_DOWN=no in a ifcfg-ethX and
dhclient will always start.
Comment 1 Paul B Schroeder 2007-03-26 17:30:42 EDT
Created attachment 150965 [details]
ifup-eth CHECK_LINK_DOWN patch
Comment 2 Bill Nottingham 2007-03-30 02:10:05 EDT
Why not just use LINKDELAY or NETWORKDELAY for your switch?
Comment 3 Paul B Schroeder 2007-03-30 02:25:25 EDT
(In reply to comment #2)
> Why not just use LINKDELAY or NETWORKDELAY for your switch?

We want devices to still come up normally if the switch is already up and the
link is present.  Wouldn't using those *always* create a delay at startup?
Comment 4 Bill Nottingham 2007-04-05 23:25:17 EDT
Hm. I'd wonder if in the case of PERSISTENT_DHCLIENT, the link status should be
ignored *by default* - I'm not sure in what case you'd actually want to ever exit.
Comment 5 Paul B Schroeder 2007-04-16 15:37:37 EDT
(In reply to comment #4)
> Hm. I'd wonder if in the case of PERSISTENT_DHCLIENT, the link status should be
> ignored *by default* - I'm not sure in what case you'd actually want to ever exit.

Didn't think about that prior..  But now that you mention it, yea, that seems to
make the most sense.
Comment 6 Bill Nottingham 2007-04-16 18:12:36 EDT
Added in CVS, will be in 8.52-1.

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