Comment 3 for bug 1372141

If my understanding is correct, this issue manifests itself when there is an interleaving router delete while binding a port:

An analysis from the logs [1] revealed these sequence of actions:

It's shown that this issue manifests itself when:

a) _ensure_host_set_on_ports is called on a router (in the example: 9706e742-84e2-4fed-b040-c577dd5622cb)
b) the router is deleted shortly after (in around 2014-12-24_00_40_32_020)
c) ports get disposed
d) the bind operations comes afterwards (in around 2014-12-24_00_40_32_607)

[1] http://logs.openstack.org/76/134676/13/check/check-tempest-dsvm-neutron-dvr/caa7479/logs/screen-q-svc.txt.gz?#_2014-12-24_00_40_31_113