Neutron port shouldn't be reprocessed if the vNIC was not found

[Claudiu Belu]

neutron-hyperv-agent relies on vNIC added / removed events from Hyper-V for binding and processing the neutron ports. For example, when a new vNIC has been created, neutron-hyperv-agent's event listener is triggered, and will proceed to process it.

If there are any problems encountered while processing it, the agent will try to reprocess it later. If the vNIC no longer exists by the time it gets to be processed, it shouldn't be reprocessed.

Trace: http://paste.openstack.org/show/623300/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/511159
Committed: https://git.openstack.org/cgit/openstack/networking-hyperv/commit/?id=805a7838367dfddabaa562176bf8cb0c568e915b
Submitter: Jenkins
Branch: master

commit 805a7838367dfddabaa562176bf8cb0c568e915b
Author: Claudiu Belu <email address hidden>
Date: Wed Oct 11 09:55:08 2017 +0300

    Stop reprocessing a neutron port if the vNIC doesn't exist

    If the vNIC is no longer found (HyperVvNicNotFound exception),
    it shouldn't be added in the _added_ports list for reprocessing.

    Change-Id: I26c93eb37f54612a24f8f8c075ae3db14444cee2
    Closes-Bug: #1722726

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/511841

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/511841
Committed: https://git.openstack.org/cgit/openstack/networking-hyperv/commit/?id=e50162fbf71e6c96f7b42df7d1cc7b61170c7864
Submitter: Jenkins
Branch: stable/pike

commit e50162fbf71e6c96f7b42df7d1cc7b61170c7864
Author: Claudiu Belu <email address hidden>
Date: Wed Oct 11 09:55:08 2017 +0300

    Stop reprocessing a neutron port if the vNIC doesn't exist

    If the vNIC is no longer found (HyperVvNicNotFound exception),
    it shouldn't be added in the _added_ports list for reprocessing.

    Change-Id: I26c93eb37f54612a24f8f8c075ae3db14444cee2
    Closes-Bug: #1722726
    (cherry picked from commit 805a7838367dfddabaa562176bf8cb0c568e915b)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-hyperv 6.0.0 release.