NetworkManager does not add interfaces back to bridge after dissconnect and then connect

[devilsclaw]

Is this a new report?

Yes

System Info

Void 6.19.10_1 x86_64 AuthenticAMD uptodate rrrmd

Package(s) Affected

NetworkManager-1.50.0_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

When disconnecting and then connecting a bridge that the slave devices and added back in on connect.

Actual behaviour

When the system boots the bridge has everything its supposed to and if running correctly.
In KDE Network Connections if I click disconnect and then click connect a few seconds later it show the bridge it up but if I do brctl show there is nothing in the bridge. I am pretty sure this worked before. the slave device it is set to automatically connect with priority 0 which is the default value for it.

Steps to reproduce

1. nmcli con add type bridge con-name br2 ifname br2
2. nmcli con add type ethernet con-name br2-eth02 ifname eth02 master br2 #NOTE: eth02 is what ever your ethernet device it eth02 just happens to be what I'm testing with right now
3. nmcli con modify br2 ipv4.addresses 192.169.1.100/24
4. nmcli con modify br2 ipv4.gateway 192.169.1.1
5. nmcli con modify br2 ipv4.dns "192.169.1.1"
6. nmcli con modify br2 ipv4.method manual
7. nmcli con up br2
8. brctl show br2 #this will show that br2 is without any interfaces
9. nmcli con up br2-eth02 #this will force the slave up
10. brctl show br2 #you will now see the eth02 or what ever your device is in interfaces

NOTE: on reboot all interfaces will be there but if you disconnect and connect of bring down and up they will not be there
nmcli con down br2
nmcli con up br2

[devilsclaw]

NOTE: If you wonder why I am even using bridges it makes life easier when running virtual machines with qemu with out having to run NAT.

[devilsclaw]

NOTE:
sudo nmcli con modify eth02-br connection.autoconnect yes
sudo nmcli con modify br2 connection.autoconnect yes

this does not solve the problem. I think the new networkmanager is ignoring this when using the up command