ovs bridge device recognition: "node <hostname> renamed interface eth0 to br0"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Medium
|
Unassigned |
Bug Description
I am using an OVS bridge on a MAAS host instead of a Linux bridge. Like with the Linux bridge, the MAC address for eth0 is the same as the one that the ovs bridge gets (00:16:3e:d2:fc:45 in this case).
root@test:~# ovs-vsctl show
19a4f3e3-
Bridge "br0"
Port "eth0"
Port "br0"
Port "vnet0"
ovs_version: "2.8.0"
root@test:~# ip a s
1: lo: <LOOPBACK,
...
2: ovs-system: <BROADCAST,
link/ether 32:ee:59:66:d6:08 brd ff:ff:ff:ff:ff:ff
3: br0: <BROADCAST,
link/ether 00:16:3e:d2:fc:45 brd ff:ff:ff:ff:ff:ff
inet 10.20.20.2/24 brd 10.20.20.255 scope global br0
valid_lft forever preferred_lft forever
inet6 fd42:5ba:
valid_lft 3476sec preferred_lft 3476sec
inet6 fe80::216:
valid_lft forever preferred_lft forever
266: eth0@if267: <BROADCAST,
link/ether 00:16:3e:d2:fc:45 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::216:
valid_lft forever preferred_lft forever
A lot of "node test renamed interface" messages are observed in regiond.log:
http://
/var/log/
The result is that MAAS considers eth0 to be the only interface present and does not properly discover an IP address assigned to br0.
The problem with not being able to discover an IP address is alleviated to some extent by using an additional internal interface:
ovs-vsctl add-br br0
ovs-vsctl add-port br0 eth0
ovs-vsctl add-port br0 svi0 -- set interface svi0 type=internal
root@test:~# ovs-vsctl show
19a4f3e3-
Bridge "br0"
Port "eth0"
Port "br0"
Port "svi0"
Port "vnet0"
ovs_version: "2.8.0"
In this case, if an address is assigned to svi0, then MAAS picks up the interface details.
The repeated message seems to be coming from:
https:/
An iftype in sysfs for an OVS bridge matches the one for Linux Bridge ("1"):
https:/
What's different is bridged_interface detection as the same sysfs entries are not available:
https:/
Another point is that regular tcpdump cannot be used to listen on ovs interfaces:
http://
/var/log/
With an additional internal interface MAAS seems to properly work with OVS used as a switch for basic use-cases.
Changed in maas: | |
status: | Invalid → New |
summary: |
- [2.3.0] ovs bridge device recognition: "node <hostname> renamed - interface eth0 to br0" + ovs bridge device recognition: "node <hostname> renamed interface eth0 + to br0" |
Changed in maas: | |
status: | New → Triaged |
milestone: | 2.4.x → none |
An attachment shows a successful internal interface (svi0) and address discovery. The address is configured in /e/n/i:
auto svi0
iface svi0 inet static
address 10.20.20.2/24
gateway 10.20.20.1
OVS interfaces can be administratively brought up via ifup and assigned addresses just like linux bridge interfaces, see also https:/ /git.io/ vbBgK