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.

Bug 2079054

Summary: NM wrongly removes all addresses on the unmanaged interface which it shouldn't
Product: Red Hat Enterprise Linux 8 Reporter: Wen Liang <wenliang>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Matej Berezny <mberezny>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 8.7CC: acabral, bgalvani, ferferna, lrintel, mberezny, rkhan, rmeggins, sukulkar, till, vbenes
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.39.5-1.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-08 10:10:31 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:

Description Wen Liang 2022-04-26 19:14:28 UTC
Description of problem:

The following test is conducting on the rhel8.7 1minutetip machine:

[root@ci-vm-10-0-139-77 ~]# ip link add name testbr type bridge forward_delay 0
[root@ci-vm-10-0-139-77 ~]# ip link set testbr up  && ip addr add 192.0.2.1/24 dev testbr && ip -6 addr add 2001:DB8::1/32 dev testbr
[root@ci-vm-10-0-139-77 ~]# ip a s testbr
7: testbr: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether ba:42:8d:29:a7:20 brd ff:ff:ff:ff:ff:ff
    inet 192.0.2.1/24 scope global testbr
       valid_lft forever preferred_lft forever
    inet6 2001:db8::1/32 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::b842:8dff:fe29:a720/64 scope link
       valid_lft forever preferred_lft forever
 
[root@ci-vm-10-0-139-77 ~]# ip l del testbr
[root@ci-vm-10-0-139-77 ~]# ip link add name testbr type bridge forward_delay 0
[root@ci-vm-10-0-139-77 ~]# nmcli d set testbr managed false
[root@ci-vm-10-0-139-77 ~]# ip link set testbr up  && ip addr add 192.0.2.1/24 dev testbr && ip -6 addr add 2001:DB8::1/32 dev testbr
[root@ci-vm-10-0-139-77 ~]# ip a s testbr
8: testbr: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 72:a4:59:1f:cb:3e brd ff:ff:ff:ff:ff:ff
    inet6 fe80::70a4:59ff:fe1f:cb3e/64 scope link
       valid_lft forever preferred_lft forever
 

Notice that the addresses can not be configured afterwards if unmanage the testbr device.



The complete log is attached. 



Version-Release number of selected component (if applicable):
[root@ci-vm-10-0-139-77 ~]# nmcli -v
nmcli tool, version 1.39.0-1.el8
[root@ci-vm-10-0-139-77 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.7 Beta (Ootpa)


How reproducible:
I can reproduce everytime


Steps to Reproduce:
1. ip link add name testbr type bridge forward_delay 0
2. nmcli d set testbr managed false
3. ip link set testbr up  && ip addr add 192.0.2.1/24 dev testbr && ip -6 addr add 2001:DB8::1/32 dev testbr
4. ip a s testbr

Actual results:
The addresses are not configured for testbr

Expected results:
The addresses are configured for testbr

Additional info:

Comment 1 Thomas Haller 2022-04-26 19:26:31 UTC
bad thing happens at 

>  [1650999988.8413] l3cfg[917a14bfe5d6d6c8,ifindex=10]: commit on idle (scheduled) (reapply)

Comment 3 Till Maas 2022-04-28 09:43:27 UTC
What's the situation with NM in RHEL 8.6 for this scenario?

Comment 4 Wen Liang 2022-04-28 16:27:38 UTC
(In reply to Till Maas from comment #3)
> What's the situation with NM in RHEL 8.6 for this scenario?

I can always reproduce the same issue in RHEL 8.6. 

```
[root@ci-vm-10-0-136-35 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.6 (Ootpa)
[root@ci-vm-10-0-136-35 ~]# nmcli -v
nmcli tool, version 1.36.0-4.el8


[root@ci-vm-10-0-136-35 ~]# ip link add name testbr type bridge forward_delay 0
[root@ci-vm-10-0-136-35 ~]# nmcli d set testbr managed false
[root@ci-vm-10-0-136-35 ~]# ip link set testbr up  && ip addr add 192.0.2.1/24 dev testbr && ip -6 addr add 2001:DB8::1/32 dev testbr
[root@ci-vm-10-0-136-35 ~]# ip a s testbr
7: testbr: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether c2:39:33:72:fe:bd brd ff:ff:ff:ff:ff:ff
    inet6 fe80::c039:33ff:fe72:febd/64 scope link 
       valid_lft forever preferred_lft forever
[root@ci-vm-10-0-136-35 ~]# 

```

Comment 5 Till Maas 2022-05-05 14:16:23 UTC
*** Bug 2079053 has been marked as a duplicate of this bug. ***

Comment 9 errata-xmlrpc 2022-11-08 10:10:31 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-2022:7680