yahoo-eng-team team mailing list archive

[John Davidge <jodavidg@xxxxxxxxx>]

Public bug reported:

The pd-notify command has been failing since
https://review.openstack.org/#/c/250487 was merged on December 9th. This
seems to be because guru_meditation_report is usurping pd-notify's use
of the SIGUSR1 signal.

pd-notify was changed from using SIGHUP to using SIGUSR1 by
https://review.openstack.org/#/c/240267/

We can't go back to using SIGHUP without breaking the l3-agent restart
function, so I would suggest using another signal such as SIGALRM.

Without pd-notify, neutron cannot learn of prefix updates received by
the pd client.

** Affects: neutron
     Importance: Undecided
     Assignee: John Davidge (john-davidge)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => John Davidge (john-davidge)

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

Title:
  Prefix Delegation pd-notify command is failing when called by dibbler-
  client

Status in neutron:
  New

Bug description:
  The pd-notify command has been failing since
  https://review.openstack.org/#/c/250487 was merged on December 9th.
  This seems to be because guru_meditation_report is usurping pd-
  notify's use of the SIGUSR1 signal.

  pd-notify was changed from using SIGHUP to using SIGUSR1 by
  https://review.openstack.org/#/c/240267/

  We can't go back to using SIGHUP without breaking the l3-agent restart
  function, so I would suggest using another signal such as SIGALRM.

  Without pd-notify, neutron cannot learn of prefix updates received by
  the pd client.

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