Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause:
If assigning of ip address through DHCPv4 fails initscript exits with error.
Consequence:
Static IPv4 and IPv6 addresses are not set if DHCPv4 fails.
Fix:
Add option IPV4_FAILURE_FATAL. This option lets user decide whether the script should continue or exit if DHCPv4 fails. Also if set to "no" and DHCPv6 is enabled in the configuration file, script tries to get IPv6 address even if DHCPv4 fails.
Result:
User has more control of what happens when DHCPv4 fails
DescriptionKonstantin Volkov
2012-06-28 12:49:38 UTC
Description of problem:
Static IPV4 and IPV6 addresses are not set to interface if DHCPv4 failed for this interface
Version-Release number of selected component (if applicable):
initscripts-9.03.31-2.el6
How reproducible:
100%
Steps to Reproduce:
1. Configure the eth0 as DHCP + static IPV4 + static IPV6:
---
CT-106-bash-4.1# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
ONBOOT="yes"
BOOTPROTO="static"
DHCPV6C="no"
IPV6INIT="yes"
IPV6ADDR_SECONDARIES="2001:aaad::a1d:8290/64"
IPADDR="1.1.1.2"
NETMASK=""
---
2. service network restart (or ifup eth0)
3. see that both IPV4 and IPV6 addresses are not assigned if dhcpv4 client failed
Actual results:
---
CT-106-bash-4.1# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:1C:42:FE:07:84
inet6 addr: fe80::21c:42ff:fefe:784/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3551808 errors:0 dropped:0 overruns:0 frame:0
TX packets:144 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:302572596 (288.5 MiB) TX bytes:20662 (20.1 KiB)
---
Expected results:
Both static addresses are assigned to eth0
Additional info:
The problem is in /etc/sysconfig/network-scripts/ifup-eth :
[...]
if /sbin/dhclient ${DHCLIENTARGS} ${DEVICE} ; then
echo $" done."
else
echo $" failed."
exit 1
fi
as you can see, all work stopped if dhclient failed. Please, fix.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-1679.html
Description of problem: Static IPV4 and IPV6 addresses are not set to interface if DHCPv4 failed for this interface Version-Release number of selected component (if applicable): initscripts-9.03.31-2.el6 How reproducible: 100% Steps to Reproduce: 1. Configure the eth0 as DHCP + static IPV4 + static IPV6: --- CT-106-bash-4.1# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE="eth0" ONBOOT="yes" BOOTPROTO="static" DHCPV6C="no" IPV6INIT="yes" IPV6ADDR_SECONDARIES="2001:aaad::a1d:8290/64" IPADDR="1.1.1.2" NETMASK="" --- 2. service network restart (or ifup eth0) 3. see that both IPV4 and IPV6 addresses are not assigned if dhcpv4 client failed Actual results: --- CT-106-bash-4.1# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1C:42:FE:07:84 inet6 addr: fe80::21c:42ff:fefe:784/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3551808 errors:0 dropped:0 overruns:0 frame:0 TX packets:144 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:302572596 (288.5 MiB) TX bytes:20662 (20.1 KiB) --- Expected results: Both static addresses are assigned to eth0 Additional info: The problem is in /etc/sysconfig/network-scripts/ifup-eth : [...] if /sbin/dhclient ${DHCLIENTARGS} ${DEVICE} ; then echo $" done." else echo $" failed." exit 1 fi as you can see, all work stopped if dhclient failed. Please, fix.