RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 585047 - IPv6 DHCP causes system boot to hang if IPv6 DHCP server is unavailable
Summary: IPv6 DHCP causes system boot to hang if IPv6 DHCP server is unavailable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: initscripts
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: Miroslav Vadkerti
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-23 01:18 UTC by Norman
Modified: 2014-09-08 11:44 UTC (History)
3 users (show)

Fixed In Version: initscripts-9.03.6-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 20:40:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
suggested patch (1.21 KB, patch)
2010-04-23 12:50 UTC, Jiri Popelka
no flags Details | Diff

Description Norman 2010-04-23 01:18:58 UTC
Description of problem:
If system is configured to use DHCP over IPv6, but DHCP server is unavailable, system hangs indefinitely.

Version-Release number of selected component (if applicable):
RHEL 6.0 beta 1


How reproducible:
100%


Steps to Reproduce:
1. DHCPV6C=yes in /etc/sysconfig/network-scripts/ifcfg-eth0
2. ensure no DHCP IPv6 server is running on network
3. reboot client
  
Actual results:
RHEL 6.0 beta 1 system hangs while trying to bring up NIC

Expected results:
'dhclient -6' should return an error and/or continue in the background

Additional info:

Comment 2 RHEL Program Management 2010-04-23 02:54:17 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Jiri Popelka 2010-04-23 12:49:36 UTC
Thank you for the report Norman.

I think the problem is not in dhclient.
I'm going to switch the component to initscripts and here is the explanation:

If the ISC client for DHCPv4 receives no response to its broadcast message
in the INIT state, it continues retransmitting DHCPDISCOVER messages
for some configurable period of time and than it either
exits (when running dhclient with -1 parameter)
or becomes a daemon (when running without -1 parameter).

If the ISC client for DHCPv6 receives no response to its Solicit message, it
continues retransmitting Solicit messages for some configurable period of
time and than it either exits (when running dhclient with -1 parameter) or
continues running in foreground (when running without -1 parameter).

When the client for DHCPv6 is started (without -1) during system startup and it
receives no response to its Solicit messages it doesn't "give up" and
holds up the system indefinitely.

I can ask upstream (ISC) if this is a bug or it is intentional,
but I think this is not important for this bug report.

What I think is important is that ifup-eth starts dhclient for DHCPv4 by default (when PERSISTENT_DHCLIENT=yes is not used) with -1 parameter.

So I suggest to start dhclient for DHCPv6 also with -1 parameter
so it will behave like the dhclient for DHCPv4.

There's also -nw parameter. man dhclient says:
"-nw    Become a daemon process immediately (nowait) rather than waiting until an IP address has been acquired."
This also solves the problem,
but I think the "-1" parameter is what we need.

Comment 4 Jiri Popelka 2010-04-23 12:50:23 UTC
Created attachment 408599 [details]
suggested patch

Comment 5 Bill Nottingham 2010-04-23 18:33:13 UTC
Merged without the echos.

Comment 8 Miroslav Vadkerti 2010-09-17 19:33:01 UTC
VERIFIED as fixed in initscripts-9.03.17-1.el6. 

service network restart now works fine and does not hang

NEW package initscripts-9.03.17-1.el6:
:: [   PASS   ] :: Running '(service network restart; echo PASS) &> /tmp/tmp.8mhQCoT3iP &'
:: [   PASS   ] :: Running 'sleep 5m'
:: [   PASS   ] :: File '/tmp/tmp.8mhQCoT3iP' should contain 'PASS'


OLD package initscripts-9.03.5-1.el6:
:: [   PASS   ] :: Running '(service network restart; echo PASS) &> /tmp/tmp.AVpvaDDujA &'
:: [   PASS   ] :: Running 'sleep 5m'
:: [   FAIL   ] :: File '/tmp/tmp.AVpvaDDujA' should contain 'PASS'

Comment 9 releng-rhel@redhat.com 2010-11-10 20:40:07 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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