Comment 2 for bug 1798472

I compared some "good" and "bad" run of ovs agent.
From what I see there it looks that this agent was already "not responding".
In "good" log there is entry about subnet_delete, then network_delete and than catch SIGTERM, see:
http://logs.openstack.org/93/615893/1/gate/neutron-fullstack/bf3dc84/logs/dsvm-fullstack-logs/TestBwLimitQoSOvs.test_bw_limit_qos_policy_rule_lifecycle_ingress,openflow-native_/neutron-openvswitch-agent--2018-11-07--11-45-30-405950.txt.gz#_2018-11-07_11_45_50_152

In "bad" run, there is info about subnet_delete and that's all - there is no info about network_delete (which happened in server) and no info about catch SIGTER, see:

http://logs.openstack.org/93/615893/1/gate/neutron-fullstack/bf3dc84/logs/dsvm-fullstack-logs/TestBwLimitQoSOvs.test_bw_limit_qos_port_removed_ingress,openflow-cli_/neutron-openvswitch-agent--2018-11-07--11-42-09-570698.txt.gz#_2018-11-07_11_42_30_454