Hide Forgot
Created attachment 484366 [details] backported patch Description of problem: A customer rebooted their system while the network switch is down. /etc/sysconfig/network-scripts/ifcfg-eth0 on the system has PERSISTENT_DHCLIENT=yes, so it's expected that dhclient starts on boot for eth0. But, it did not start. As a result, even after the network switch starts to work, the network interface eth0 did not link up automatically. ifup-eth script in upstream initscripts has the fix to start dhclient upon a value of PERSISTENT_DHCLIENT. I will attach the backported patch on this bugzilla. Version-Release number of selected component (if applicable): RHEL5.6 initscripts-8.45.33-1.el5 How reproducible: Always Steps to Reproduce: 1. configure PERSISTENT_DHCLIENT=yes for eth0 2. ifdown eth0 3. remove the ethernet cable from eth0 4. ifup eth0, and confirm if dhclient is running. Actual results: dhclient does not start even when PERSISTENT_DHCLIENT=yes is configured for eth0 Expected results: dhclient starts with PERSISTENT_DHCLIENT=yes. Additional info:
For reference, that's ca5bd7279c61f0b7dd5083d9ffab85fc2e0858ba in git.
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.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When a system was rebooted while the network switch was down and the network interface had the PERSISTENT_DHCLIENT variable set to "yes", the dhclient utility still failed to start on boot. With this update, the ifup-eth init script has been fixed and the dhclient utility starts as expected when "PERSISTENT_DHCLIENT=yes" is configured.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1081.html