> Another question: is there a canonical way to determine if OVS isn't up? Currently I'm trying to execute a command and looking for "database connection failed" in the output, is that appropriate?
In the Ubuntu systemd service we assess the database socket: https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/openvswitch/tree/debian/openvswitch-switch.ovs-vswitchd.service#n7 But I guess assessing tools most likely to be in your path would be more portable, so calling `ovs-vsctl` and assessing the result would work ok. One thing to keep in mind is that the OVS/OVN -ctl tools may get into a situation where they wait indefinitely. That can for example happen if the OVSDB server is running but the vSwitch is not. To mitigate that you can use the -t or --timeout option when calling `ovs-vsctl`. To assess whether the `ovs-vswitchd` process is alive independently of the OVSDB you could have an additional check that talks to it on its control socket, for example: `ovs-appctl -t ovs-vswitchd version` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912844 Title: Bond with OVS bridging RuntimeError: duplicate mac found! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
