Binding entry of router to hosting device not found in DB table

[Bob Melander]

AKA: DE2296

2016-06-19 05:15:38.920 ERROR oslo.service.loopingcall [req-18f32b84-43b0-4545-9b85-ce0c333569b1 None None] Fixed interval looping call 'networking_cisco.plugi

ns.cisco.service_plugins.cisco_router_plugin.CiscoRouterPlugin._process_backlogged_routers' failed

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall Traceback (most recent call last):

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall File "/usr/local/lib/python2.7/dist-packages/oslo_service/loopingcall.py", line 136, in _run_loop

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall result = func(*self.args, **self.kw)

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall File "/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py", line 271, in inner

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall return f(*args, **kwargs)

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall File "/opt/stack/networking-cisco/networking_cisco/plugins/cisco/db/l3/l3_router_appliance_db.py", line 881, in _process_backlogged_routers

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall r_hd_binding = self._get_router_binding_info(e_context, r_id)

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall File "/opt/stack/networking-cisco/networking_cisco/plugins/cisco/db/l3/l3_router_appliance_db.py", line 1131, in _get_router_binding_info

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall raise RouterBindingInfoError(router_id=id)

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall RouterBindingInfoError: Could not get binding information for router e4f3ddea-b026-4ef6-9eba-c72f1ebf71f0.

2016-06-19 05:15:38.920 TRACE oslo.service.loopingcall

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/335566
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=dd262b0499313aafe8328d376cff20fe346a91b3
Submitter: Jenkins
Branch: master

commit dd262b0499313aafe8328d376cff20fe346a91b3
Author: Bob Melander <email address hidden>
Date: Tue Jun 21 15:13:01 2016 +0200

    Handle deleted router gracefully when processing router backlog

    A router in the router backlog may have been deleted by a
    concurrent server process. In that case the backlog processing
    task will fail when it tries to fetch the information about
    the deleted router.

    This patch handles that situation by catching the exception,
    logging it, and then aborting the processing attempt for the
    deleted router

    AKA: DE2296

    Closes bug: #1595644

    Change-Id: I1dd259cb1a2a67142cbeee4b4537bd1c15d3a352