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 1816517 - Bridge slave still have IPv6 address after enslaved
Summary: Bridge slave still have IPv6 address after enslaved
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: 8.3
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: nmstate-nm
TreeView+ depends on / blocked
 
Reported: 2020-03-24 08:03 UTC by Gris Ge
Modified: 2020-11-04 01:50 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.25.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:49:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Reproduce script (1.50 KB, text/x-python)
2020-03-24 08:03 UTC, Gris Ge 		no flags Details
System logs with NM trace enabled (NetworkManager-1.23.2-25243.e75d62ce76.el8.x86_64) (258.25 KB, text/plain)
2020-03-24 08:30 UTC, Gris Ge 		no flags Details
Reproducer using iproute2 and nmcli (923 bytes, application/x-shellscript)
2020-04-27 07:26 UTC, Beniamino Galvani 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4499 0 None None None 2020-11-04 01:50:03 UTC

Description Gris Ge 2020-03-24 08:03:32 UTC 
Created attachment 1672960 [details]
Reproduce script

Description of problem:

When a dummy interface got enslaved into bridge, it still has its IPv6 link local address.

Version-Release number of selected component (if applicable):
NetworkManager-1.23.2-25243.e75d62ce76.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. sudo ./update2_bug.py
2.
3.

Actual results:

The `dummy1` interface still has IPv6 address.

Expected results:

The `dummy1` interface has no IPv4/IPv6 address.

Additional info:
Comment 1 Thomas Haller 2020-03-24 08:12:58 UTC 
Thanks for the reproducer script. But could you also provide the full level=TRACE logfile? See https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28 for hints about logging. Also, the reproducer script prints output, can you show that too? It's probably not necessary in this case, but usually the output of `ip link`, `ip addr`, `nmcli connection`, `nmcli device` is very helpful too. Thank you!!
Comment 2 Gris Ge 2020-03-24 08:27:37 UTC 
The output is:

```
7: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue master test-network state UNKNOWN group default qlen 1000
    link/ether d6:b5:37:12:33:bc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::d4b5:37ff:fe12:33bc/64 scope link
       valid_lft forever preferred_lft forever

7: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 master test-network state forwarding priority 32 cost 100
```
Comment 3 Gris Ge 2020-03-24 08:30:08 UTC 
Created attachment 1672962 [details]
System logs with NM trace enabled (NetworkManager-1.23.2-25243.e75d62ce76.el8.x86_64)
Comment 4 Gris Ge 2020-04-20 14:50:31 UTC 
Nmstate can do a workaround to hide this during verification, but still need it been fixed.
Comment 5 Beniamino Galvani 2020-04-27 07:23:59 UTC 
Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/480
Comment 6 Beniamino Galvani 2020-04-27 07:26:47 UTC 
Created attachment 1682049 [details]
Reproducer using iproute2 and nmcli
Comment 7 Beniamino Galvani 2020-04-28 08:07:48 UTC 
Fixed:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/e302f5ff77a9c6cc57c332e8274ce05ac85cf608

The commit will be in NM 1.22.12 and 1.24.0.
Comment 10 Vladimir Benes 2020-07-01 10:04:42 UTC 
test case added:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/590
Comment 13 errata-xmlrpc 2020-11-04 01:49:27 UTC 
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 (NetworkManager bug fix and enhancement update), 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-2020:4499
Note You need to log in before you can comment on or make changes to this bug.