Why OVS bridge fails after a reboot on Windows 2016?

asked 2018-04-13 17:52:03 +0200

darmachj gravatar image

updated 2018-04-13 17:53:58 +0200

We're creating an ovs bridge, and then a bond on Windows 2016 Core:

ovs-vsctl add-br br0
ovs-vsctl add-bond br0 bond0 "Ethernet" "Ethernet 1" bond_mode=balance-slb
Enable-NetAdapter br0
New-NetIPAddress -InterfaceAlias "br0" -IPAddress XX.XX.XX.XX -PrefixLength 26

Everything works fine up to the point when we reboot the server, after the reboot the interface is not restored, ovs-vsctl show returns the error:

ovs-vsctl show
    Bridge br0
        Port br0
            Interface br0
                type: internal
                error: "could not add network device br0 to ofproto (Invalid argument)"
        Port "bond0"
            Interface "Ethernet 4"
            Interface Ethernet

Can anyone advise what might be happening?

edit retag flag offensive close merge delete

Comments

Can you tell us which version of OVS are you using? You can use the following command as reference: ovs-vsctl -v

aserdean gravatar imageaserdean ( 2018-04-16 18:49:25 +0200 )edit

We're running beta 2.7.4 - issue was initially encountered on 2.7.0

darmachj gravatar imagedarmachj ( 2018-04-16 21:18:51 +0200 )edit

Does the issue still reproduce on 2.7.4? On 2.7.0 as far as I know there was some issues when restarting, the normal workaround is to restart the ovs-vswitchd service.

aserdean gravatar imageaserdean ( 2018-04-16 22:49:37 +0200 )edit

Yes, we're on 2.7.4 now and the issue still persist.

darmachj gravatar imagedarmachj ( 2018-04-17 10:44:05 +0200 )edit

Can you please post the ovs-vswitchd.log?

aserdean gravatar imageaserdean ( 2018-04-17 14:27:19 +0200 )edit
darmachj gravatar imagedarmachj ( 2018-04-20 18:30:40 +0200 )edit

Can you please repost it. The log expired :(.

aserdean gravatar imageaserdean ( 2018-04-23 13:29:51 +0200 )edit