I added a vif to a ethernet interface, committed, and the ethernet interface dropped out of the bridge. I had to go to the console to delete and re-add the member interfaces.
```
vyos@rt-home:~$ show bridge
bridge name bridge id STP enabled interfaces
br0 5000.0019xxxxxxxx yes eth0
eth1
eth2
vyos@rt-home# set interfaces ethernet eth1 vif 20
[edit]
vyos@rt-home# set interfaces ethernet eth2 vif 20
[edit]
vyos@rt-home# commit
[edit]
(lost connection here, had to go log in to the physical console)
vyos@rt-home:~$ show bridge
bridge name bridge id STP enabled interfaces
br0 5000.001921dffc1e yes eth0
[edit]
vyos@rt-home# delete interfaces bridge br0 member interface eth1
[edit]
vyos@rt-home# delete interfaces bridge br0 member interface eth2
[edit]
vyos@rt-home# commit
[edit]
vyos@rt-home# add interfaces bridge br0 member interface eth1
[edit]
vyos@rt-home# add interfaces bridge br0 member interface eth2
[edit]
vyos@rt-home# commit
[edit]
vyos@rt-home# run show bridge br0
bridge name bridge id STP enabled interfaces
br0 5000.0006xxxxxxxx yes eth0
eth1
eth2
eth4
```
```
vyos@rt-home# show interfaces bridge |strip-private
bridge br0 {
address xxx.xxx.0.1/24
address xxxx:xxxx::1/64
aging 300
description LAN
firewall {
local {
name lan-local
}
}
hello-time 2
ipv6 {
dup-addr-detect-transmits 2
}
max-age 20
member {
interface eth0 {
}
interface eth1 {
}
interface eth2 {
}
interface eth4 {
}
}
priority 20480
stp
}
```
Edit 2020-04-24: this also happens if changing any setting on an ethernet interface, like removing an address, not just adding a vif to it. Retested with latest rolling code to still be an issue.