Comment 19 for bug 1697243

the issue is 100% reproducible when rebooting server.
my service boot sequence after rebooting server is as following:

1.neutron_openvswitch_agent
2.neutron_dhcp_agent
3.neutron_l3_agent
4.neutron_server

the services are run in a script after server has been booted, so I can control sequence and check flow table easily.

I found two facts:

1)flow tables of all ovs bridge were normal after step1,2.
2)only after step3 the flow table of "provider" became empty.

It seems neutronp_l3_agent service make flow table emty.