Bug 1816517

Summary: Bridge slave still have IPv6 address after enslaved
Product: Red Hat Enterprise Linux 8 Reporter: Gris Ge <fge>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 8.2CC: acardace, atragler, bgalvani, lrintel, rkhan, sukulkar, thaller, till, vbenes
Target Milestone: rc   
Target Release: 8.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-1.25.1-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 01:49:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1738136    
Attachments:
Description Flags
Reproduce script
none
System logs with NM trace enabled (NetworkManager-1.23.2-25243.e75d62ce76.el8.x86_64)
none
Reproducer using iproute2 and nmcli none

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 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