yahoo-eng-team team mailing list archive

["maxiao@xxxxxxxxxxxxxxx" <maxiao@xxxxxxxxxxxxxxx>]

Public bug reported:

When the L3 Agent is restarting, the function get_routers will be called
to get all the routers information which is called full-sync.

But when the RPC request is excuted in the Neutron Server side,the function stacks bellow called:
l3_rpc.py:sync_routers-->l3_dvr_db.py:get_sync_data-->l3_dvr_db.py:get_vm_port_hostid-->self._core_plugin.get_port 

So,If the floating ip of the port has been deleted just right,the
self._core_plugin.get_port will raise exception.

The exception will not be expected. So this will make the L3 Agent be
interrupted and it have to sync all the routers next cycle.

** Affects: neutron
     Importance: Undecided
     Assignee: maxiao@xxxxxxxxxxxxxxx (maxiao)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => maxiao@xxxxxxxxxxxxxxx (maxiao)

** Changed in: neutron
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1390920

Title:
  PortNotFound exception makes the L3 Agent full-sync failed

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  When the L3 Agent is restarting, the function get_routers will be
  called to get all the routers information which is called full-sync.

  But when the RPC request is excuted in the Neutron Server side,the function stacks bellow called:
  l3_rpc.py:sync_routers-->l3_dvr_db.py:get_sync_data-->l3_dvr_db.py:get_vm_port_hostid-->self._core_plugin.get_port 

  So,If the floating ip of the port has been deleted just right,the
  self._core_plugin.get_port will raise exception.

  The exception will not be expected. So this will make the L3 Agent be
  interrupted and it have to sync all the routers next cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1390920/+subscriptions