Comment 27 for bug 1697243

Sorry now I haven't chance to try your code because the environment hasn't been existed.

I guess the cause may be from the following usage of ovs bridge:

1.bond0 is built from eth0 and eth1, vlan17 is a vlan interface based on bond0.
2.bond0 is added into ovs bridge "provision"
3.vlan17 is added into ovs bridge "provider"

In this scene, flow table often be dropped on "provision" or "provider".

After I use only one ovs bridge, no any issue.

then I change my solution about network and remove "provider" bridge for escaping the above scene of "provision" and "provider" are existed on same times in one server.