yahoo-eng-team team mailing list archive

[Oleg Bondarev <obondarev@xxxxxxxxxxxx>]

Public bug reported:

Currently router_added_to_agent (and other) notifications are sent to
agents with an RPC cast() method which does not ensure that the message
is actually delivered to the recipient. If the message is lost (for
example due to instability of messaging system during failover
scenarios) neither server nor agent will be aware of that and router
namespace will not be created by the hosting agent till the next resync.
Resync will only happen in case of errors on agent side or restart which
might take quite a long time.

The proposal would be to use RPC call() to notify agents about added
routers thus ensuring no routers will be lost by agents.

** Affects: neutron
     Importance: Undecided
     Assignee: Oleg Bondarev (obondarev)
         Status: New


** Tags: l3-ipam-dhcp

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

Title:
  Router resources lost after rescheduling

Status in neutron:
  New

Bug description:
  Currently router_added_to_agent (and other) notifications are sent to
  agents with an RPC cast() method which does not ensure that the
  message is actually delivered to the recipient. If the message is lost
  (for example due to instability of messaging system during failover
  scenarios) neither server nor agent will be aware of that and router
  namespace will not be created by the hosting agent till the next
  resync. Resync will only happen in case of errors on agent side or
  restart which might take quite a long time.

  The proposal would be to use RPC call() to notify agents about added
  routers thus ensuring no routers will be lost by agents.

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