DHCP sync retriggered when deleted network was not found

[Salvatore Orlando]

Failure reference: http://logs.openstack.org/94/67994/3/check/check-tempest-dsvm-neutron-full/88959e7

This was apparently fixed with commit id f1b9ac5a542a3125d757094fccda80c80c6dd420

However if there is a NetworkNotFound exception from the server need_resync is set to True.
It seems the commit message says it the resync should not be triggered in this case.

Apparently occured only once in 48 hours, but it's hard to define a logstash query for this.

Also it might be good to understand why the port_create_notification is apparently not processed:
http://logs.openstack.org/94/67994/3/check/check-tempest-dsvm-neutron-full/88959e7/logs/screen-q-dhcp.txt.gz#_2014-02-21_19_01_10_965

The latter might be related to this or a bug on its own.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/80276

[Mark McClain (markmcclain)]

The incidence rate is super low and may not occur outside of testing. Removing the RC1 target, but if it merges before Icehouse closes will add back.

[Cedric Brandily (cbrandily)]

This bug is > 365 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]