Comment 17 for bug 1912844

Thanks Frode, that's really helpful!

I don't see the `datapath_type` in my output:

e2d9c9b4-739c-4333-a372-4d46585fcfb9
    Bridge ovs-br
        fail_mode: standalone
        Port ovs-br
            Interface ovs-br
                type: internal
        Port bond0
            Interface bond0
        Port ovs-br.100
            tag: 100
            Interface ovs-br.100
                type: internal
    ovs_version: "2.13.1"

but I _do_ see /sys/class/net/ovs-system in the system:

# ls /sys/class/net/ -lah
total 0
drwxr-xr-x 2 root root 0 Feb 9 22:07 .
drwxr-xr-x 31 root root 0 Feb 9 22:07 ..
lrwxrwxrwx 1 root root 0 Feb 9 22:07 bond0 -> ../../devices/virtual/net/bond0
-rw-r--r-- 1 root root 4.0K Feb 9 22:07 bonding_masters
lrwxrwxrwx 1 root root 0 Feb 9 22:07 enp5s0 -> ../../devices/pci0000:00/0000:00:01.4/0000:05:00.0/virtio10/net/enp5s0
lrwxrwxrwx 1 root root 0 Feb 9 22:07 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx 1 root root 0 Feb 9 22:07 ovs-br -> ../../devices/virtual/net/ovs-br
lrwxrwxrwx 1 root root 0 Feb 9 22:07 ovs-br.100 -> ../../devices/virtual/net/ovs-br.100
lrwxrwxrwx 1 root root 0 Feb 9 22:07 ovs-system -> ../../devices/virtual/net/ovs-system

If I launch a separate system, and install openvswitch-switch, /sys/class/net/ovs-system does _not_ appear, which appears to confirm that it will only be present in systems with OVS configuration.

This leads me to some questions: Will /sys/class/net/ovs-system always be present? Or might we encounter systems where only ovs-netdev (or another) is present? If so, is there a defined set we can match on, or do we need to glob match?