Hi guys.
I have both(and probably other relevant components pulled in)
NetworkManager and openvswitch2.11 from ovirt-4.4-copr and
cannot confirm if the problem is exclusive to ovirt-4 but I
thought this here is where I should start a quest for help.
I use NM to set up OVS' bridges and pretty straightforward setup
I believe, yet each time after system reboot one (always the
same) interface fails to start and stays in a weir state,
actually it gets duplicated.
ovs0-int-10.3.3 d9c9268f-408c-4035-9684-97e4eaf92e18
ovs-interface ovs0-int33 (colored yellow)
ovs0-int-10.3.3 d9c9268f-408c-4035-9684-97e4eaf92e18
ovs-interface ovs0-int33 (colored red)
whereas the rest of the bridge:
ovs0-int-10.1.1 be5e79e7-2e4e-47ed-97d0-270c76e43b9a
ovs-interface ovs0-int11
ovs0 9cf72215-eebc-4f7c-9466-b697f09e1bda
ovs-bridge ovsbr0
ovs0-port-11 1577414e-7eeb-41bc-a66f-7b7b596285d0
ovs-port ovs0-port11
ovs0-port-33 5465d3c5-9a0c-4f78-89c0-de94b0294d0e
ovs-port ovs0-port33
ovs0-port9 b9c2b7cd-897e-4726-8fc7-e2f7c7aab067
ovs-port ovs0-port9
ovs0-port9-physical 14fb0b0e-f7bb-4248-9295-34f561058f4d
ethernet enp7s0f1np1
ovsbr0-libvirt0-int f217cd6c-976b-4002-b191-9f15271602cd
ovs-interface ovsbr0
ovsbr0-libvirt0-port 7c2d30bd-0019-4cdb-af05-3df666005261
ovs-port ovsbr0
And then only another reboot with either:
a) deletion of the interface prior to reboot and after the
reboot creation anew
b) removal of /etc/openvswitch/conf.db prior to reboot.
When all is good and whole bridge is up & running then
bridge looks like this:
004e89ac-4c45-4a33-9347-c1d343889ceb
Bridge "ovsbr0"
Port "ovs0-port11"
tag: 11
Interface "ovs0-int11"
type: internal
Port "ovsbr0"
Interface "ovsbr0"
type: internal
Port "ovs0-port9"
Interface "enp9s0f3"
type: system
Port "vnet0"
tag: 33
Interface "vnet0"
Port "ovs0-port33"
tag: 33
Interface "ovs0-int33"
type: internal
ovs_version: "2.11.0"
journal does not tells much, at least not by default
....
device (ovs0-int33): Activation: starting connection
'ovs0-int-10.3.3' (d9c9268f-408c-4035-9684-97e4eaf92e18)
....
nmcli shows:
...
GENERAL.STATE: activating
...
and also:
...
GENERAL.STATE: deactivating
...
at the same time as the interface is duplicated so are GENERAL
entries.
I'm on Centos8(no Stream) and with kernel-ml.
It feels (I have no lab where I could fiddle more) that this
should reproduce. I have a second system with slightly different
hardware and this same problem occurs.
Any suggestions on how to troubleshoot and/or solve it I'd
greatly appreciate.
many thanks, L.