Description of problem:
See also bz1245951.
While iface inicialization when dad fails, ipv6 address remains tentative and script remains in the loop for 30s logging
INFO : [ipv6_wait_tentative] Waiting for interface eth0 IPv6 address(es) to leave the "tentative" state
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. stop NetworkManager
2. configure two ifaces to same ipv6 address
3. bring up both devices
takes 30s to ifup the second device
ifup exits when address is in dadfailed state
network-functions-ipv6 uses following command to detect tentative addresses, but should ignore dadfailed ones.
# ip -6 addr show dev eth0 scope global tentative
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 aaaa:bbbb:cccc::1234/64 scope global tentative dadfailed
valid_lft forever preferred_lft forever
Created attachment 1205240 [details]
I have rewritten the previously patched code, to test for dadfailed.
+ added info output in case the interface is still in tentative state after the loop ends
+ refactored the code a little
Created attachment 1207172 [details]
New version of the patch. I have fixed the missing variable name in if-condition, and corrected the error message.
Pull-request has been merged into upstream:
With initscripts-9.49.39-1.el7 bringing iface with duplicate ipv6 immediately exits with following output:
INFO : [ipv6_wait_tentative] Waiting for interface eth0 IPv6 address(es) to leave the 'tentative' state
ERROR : [ipv6_wait_tentative] Duplicate Address Detection: Duplicate addresses detected
ERROR : [ipv6_wait_tentative] Duplicate Address Detection: Please, fix your network configuration
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.