NSX: sync thread catches wrong exceptions on not found in db elements

[Aaron Rosen]

2014-04-17 14:13:07.361 ERROR neutron.openstack.common.loopingcall [req-47b42334-8484-48c9-9f3e-e6ced3b9e3ec None None] in dynamic looping call
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall Traceback (most recent call last):
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall File "/opt/stack/neutron/neutron/openstack/common/loopingcall.py", line 123, in _inner
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall idle = self.f(*self.args, **self.kw)
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall File "/opt/stack/neutron/neutron/plugins/vmware/common/sync.py", line 649, in _synchronize_state
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall scan_missing=scan_missing)
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall File "/opt/stack/neutron/neutron/plugins/vmware/common/sync.py", line 508, in _synchronize_lswitchports
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall ext_networks=ext_nets)
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall File "/opt/stack/neutron/neutron/plugins/vmware/common/sync.py", line 464, in synchronize_port
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall neutron_port_data['id'])
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall File "/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 271, in _get_port
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall raise n_exc.PortNotFound(port_id=id)
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall PortNotFound: Port 0b9ce706-1197-460d-986e-98870bc81ce7 could not be found
2014-04-17 14:13:07.361 TRACE neutron.openstack.common.loopingcall

[Openstack Gerrit (openstack-gerrit)]

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

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/88450
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=25c79b0ee78639a8abd9ab81c016ed26ba70a5d7
Submitter: Jenkins
Branch: master

commit 25c79b0ee78639a8abd9ab81c016ed26ba70a5d7
Author: Aaron Rosen <email address hidden>
Date: Thu Apr 17 14:48:55 2014 -0700

    NSX: sync thread catches wrong exceptions on not found

    Previously the sync code expected exc.NoResultFound to be raised if a
    port/router/network was not found in the database. This is actually not the
    correct exception raised. This error will only occur if an element is deleted
    from the db right when the sync thead is run for a specific element.

    Change-Id: I3a5c8316ade49004fb9fa0b454435205c543f6ee
    Closes-bug: 1309208

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/icehouse
Review: https://review.openstack.org/144311

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/144311
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ed3d4efb1f4386ec3a3aa656e541abf1ae97d793
Submitter: Jenkins
Branch: stable/icehouse

commit ed3d4efb1f4386ec3a3aa656e541abf1ae97d793
Author: Aaron Rosen <email address hidden>
Date: Thu Apr 17 14:48:55 2014 -0700

    NSX: sync thread catches wrong exceptions on not found

    Previously the sync code expected exc.NoResultFound to be raised if a
    port/router/network was not found in the database. This is actually not the
    correct exception raised. This error will only occur if an element is deleted
    from the db right when the sync thead is run for a specific element.

    Change-Id: I3a5c8316ade49004fb9fa0b454435205c543f6ee
    Closes-bug: 1309208
    (cherry picked from commit 25c79b0ee78639a8abd9ab81c016ed26ba70a5d7)