yahoo-eng-team team mailing list archive

[Takashi Kajinami <2116102@xxxxxxxxxxxxxxxxxx>]

While this can be technically fixed in every service, IMO we SHOULD revert the change.
The change made the "f" argument accepted only as a keyword argument and breaks "a lot" of existing usage found in multiple repos.

https://codesearch.opendev.org/?q=FixedIntervalLoopingCall&i=nope&literal=nope&files=&excludeFiles=&repos=

** Also affects: oslo.service
   Importance: Undecided
       Status: New

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

Title:
  Fixed interval looping call 'builtins.NoneType' failed: TypeError:
  'NoneType' object is not callable

Status in neutron:
  New
Status in oslo.service:
  In Progress

Bug description:
  Since [1], the oslo-service master jobs with ML2/OVS are failing. The
  DHCP agent and the L3 agent are failing with the following error:
  https://paste.opendev.org/show/bDcxw5x6PCSn3tuzsgxR/.

  Logs:
  * DHCP agent: https://e63f38b8e486b9ef8a45-283f569f7129297b2f76cddb21d3fd12.ssl.cf2.rackcdn.com/openstack/94e9518c947c420197c7f5184680e911/controller/logs/screen-q-agt.txt
  * L3 agent: https://e63f38b8e486b9ef8a45-283f569f7129297b2f76cddb21d3fd12.ssl.cf2.rackcdn.com/openstack/94e9518c947c420197c7f5184680e911/controller/logs/screen-q-l3.txt

  [1]https://review.opendev.org/c/openstack/oslo.service/+/952607

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