Description of problem:
After disabling userspace_tso in OVS-DPDK datapath (meaning it was enabled before) and restarting openvswitch service leads too many attempts on destroying connection (to the qemu-kvm).

Below message is repeating in ovs-vswitchd.log:
2020-05-07T06:16:01.648Z|02465|netdev_dpdk|INFO|vHost Device '/var/lib/vhost_sockets/vhuc10acbd9-89' connection has been destroyed
2020-05-07T06:16:01.648Z|02466|dpdk|INFO|Dropped 4755 log messages in last 0 seconds (most recently, 0 seconds ago) due to excessive rate

Version-Release number of selected component (if applicable):
openvswitch2.13-2.13.0-18flim.el8.x86_64

How reproducible:
Every time following steps below.

Steps to Reproduce:
1. If TSO is not enabled, do so in ovs-dpdk.
   sudo ovs-vsctl set Open_vSwitch . other_config:userspace-tso-enable=true

2. Launch a VM with vhost-user socket in server mode.
   Eg. <source type='unix' path='/var/lib/vhost_sockets/vhue8ff400b-30' mode='server'/> in libvirt xml.

   If in OSP, create instance.

3. Ensure guest kernel driver is able to detect TSO.
   sudo ethtool -k eth2 | egrep '(scatter|tcp|gso|csum|check|segment)'
   Check "on" for tx-checksumming, scatter-gather, tcp-segmentation-offload

4. Disable TSO in ovs-dpdk.
   sudo ovs-vsctl set Open_vSwitch . other_config:userspace-tso-enable=false

5. Restart openvswitch.
   sudo systemctl restart openvswitch.service

6. Check /var/log/messages/ovs-vswitchd.service for repeating messages as reported in problem statement.

Actual results:
Repeating calls to destroy_connection.

Expected results:
No too many attempts on destroying vhost-user connection.

Additional info: