Comment 4 for bug 1943863

Tried downgrading openvswitch debs: https://paste.ubuntu.com/p/fk2pfQyxDK/

After that, the original issue isn't there anymore (e.g DPDK instance could be scheduled). However, it still lacks a network connectivity.

What I've spotted is that after the VM creation, OVS service has been restarted (I guess it shouldn't do so?)

# service ovs-vswitchd status
● ovs-vswitchd.service - Open vSwitch Forwarding Unit
     Loaded: loaded (/lib/systemd/system/ovs-vswitchd.service; static; vendor preset: enabled)
     Active: activating (start) since Fri 2021-09-17 12:18:52 UTC; 4s ago
Cntrl PID: 936872 (ovs-ctl)
      Tasks: 16 (limit: 37276)
     Memory: 159.6M
     CGroup: /system.slice/ovs-vswitchd.service
             ├─936872 /bin/sh /usr/share/openvswitch/scripts/ovs-ctl --no-ovsdb-server --no-monitor --system-id=random --no-record-hostname start
             ├─936911 ovs-vswitchd unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --no-chdir --log-file=/var/log/openv>
             └─936912 ovs-vswitchd unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --no-chdir --log-file=/var/log/openv>

It also might be a red herring, but another suspicious error is present in the logs:

2021-09-17T12:18:56.458Z|00077|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on genev_sys_6081 device failed: No such device
2021-09-17T12:18:56.458Z|00078|bridge|INFO|bridge br-int: added interface ovn-u0400s-8 on port 12
2021-09-17T12:18:56.462Z|00079|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on genev_sys_6081 device failed: No such device
2021-09-17T12:18:56.463Z|00080|bridge|INFO|bridge br-int: added interface ovn-u0400s-6 on port 10
2021-09-17T12:18:56.467Z|00081|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on genev_sys_6081 device failed: No such device
2021-09-17T12:18:56.467Z|00082|bridge|INFO|bridge br-int: added interface ovn-u0400s-7 on port 11
2021-09-17T12:18:56.471Z|00083|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on genev_sys_6081 device failed: No such device
2021-09-17T12:18:56.479Z|00084|dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 21 created.
2021-09-17T12:18:56.485Z|00085|dpif_netdev|INFO|PMD thread on numa_id: 1, core id: 88 created.
2021-09-17T12:18:56.485Z|00086|dpif_netdev|INFO|There are 1 pmd threads on numa node 0
2021-09-17T12:18:56.485Z|00087|dpif_netdev|INFO|There are 1 pmd threads on numa node 1

Removed the VM, cleared the logs, re-created the VM:

echo '' > /var/log/openvswitch/ovs-vswitchd.log
openstack server create --config-drive true --network ext_net_dpdk --key-name ubuntu-keypair --image auto-sync/ubuntu-focal-20.04-amd64-server-20210907-disk1.img --flavor m1.medium.dpdk dpdk-test-instance

it's restarting again...

# service ovs-vswitchd status
● ovs-vswitchd.service - Open vSwitch Forwarding Unit
     Loaded: loaded (/lib/systemd/system/ovs-vswitchd.service; static; vendor preset: enabled)
     Active: activating (start) since Fri 2021-09-17 12:24:40 UTC; 3s ago

but the patch interface and DPDK bonds are present: https://paste.ubuntu.com/p/FN5GbbhmBS/
ovs-vswitchd.log: https://paste.ubuntu.com/p/XTZT8HCQPz/ (capture start: log cleanup, capture end: VM is in ACTIVE state)