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.

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):
initscripts-9.49.37-1.el7

How reproducible:
always

Steps to Reproduce:
1. stop NetworkManager
2. configure two ifaces to same ipv6 address
3. bring up both devices

Actual results:
takes 30s to ifup the second device

Expected results:
ifup exits when address is in dadfailed state

Additional info:
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]
exit-immediately-when-dadfailed.patch

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]
exit-immediately-when-dadfailed.patch

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:
https://github.com/fedora-sysv/initscripts/commit/eb1a9ae171f8be0137c146b9

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.

https://access.redhat.com/errata/RHBA-2017:2286