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.
Created attachment 1455495[details]
[logfile] show issue
This used NM from master (commit bf7b941502), with running
./nmcli/runtest.sh ipv6_keep_external_routes
from NM-ci (commit 83bc1631496ef4beee687cf911e7b0d427824798)
(In reply to Thomas Haller from comment #3)
> Created attachment 1455495[details]
> [logfile] show issue
at [1530268706.4408] we see the address fc00:a::10/64 externally added... then:
device[0x55a7a8f19b60] (eth3): linklocal6: generated EUI-64 IPv6LL address fe80::5054:ff:feba:f4fc
device[0x55a7a8f19b60] (eth3): ip6-config: update (commit=1, new-config=0x55a7a8f88220)
platform: address: deleting IPv6 address fc00:a::10/64, ifindex 5 dev eth3
(note, that at that point, eth3's NMDevice state was:
[1530268604.8760] device (eth3): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oddly, when I try this manually, I can reproduce it easily. But the CI tests in jenkins often pass this test. The reason is unknown. This is essentially a race, but odd that it happens commonly in the manual case and commonly not in the automated case.
With https://github.com/NetworkManager/NetworkManager/pull/144, in particular commit "device: only check for IPv6 DAD and link-local address on actively..." I didn't not reproduce the issue anymore.
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-2018:3207