yahoo-eng-team team mailing list archive

[Brian Haley <1847203@xxxxxxxxxxxxxxxxxx>]

We have since updated the l3-agent to better log when it starts/stops
processing messages, so there is at least a way to look at the logs and
help determine what happened. That said, as only this one user has seen
this issue and it was on an older release, I'll close this as there have
been no other reports (and might have been fixed in any number of
changes). If you still see if on a newer release please re-open this bug
with more information.

** Changed in: neutron
       Status: New => Invalid

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

Title:
  l3-agent stops processing router updates

Status in neutron:
  Invalid

Bug description:
  In our work on upgrading from Queens to Rocky, we have stumbled upon
  some weird behaviour in neutron-l3-agent. After "a while" (usually
  ~days), the l3-agent will simply stop processing router updates. In
  the debug log, we see:

  Got routers updated notification
  :[u'1dea9d84-e5ec-44be-b37f-7f9070dd159e'] routers_updated
  /usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py:446

  But then nothing happens after that. We're testing this with adding
  and removing a floating IP.

  The problem is that we really have noe clue what happens, other than
  the observed symptoms, so we can't really provide a way to reproduce
  this..

  neutron-l3-agent     2:13.0.4-0ubuntu1~cloud0
  openvswitch-switch   2.10.0-0ubuntu2~cloud0

  Ubuntu 18.04 LTS, running the 4.15.0-51-generic kernel

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