yahoo-eng-team team mailing list archive

[Alan Pevec <1398779@xxxxxxxxxxxxxxxxxx>]

** Also affects: neutron/juno
   Importance: Undecided
       Status: New

** Changed in: neutron/juno
       Status: New => Fix Committed

** Tags removed: in-stable-juno juno-backport-potential

** Changed in: neutron/juno
     Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka)

** Changed in: neutron/juno
   Importance: Undecided => High

** Changed in: neutron/juno
    Milestone: None => 2014.2.2

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

Title:
  radvd >= 2.0 blocks router update processing

Status in OpenStack Neutron (virtual network service):
  Fix Released
Status in neutron juno series:
  Fix Committed

Bug description:
  In radvd 2.0+, daemonization code was rewritten, switching from
  libdaemon's daemon_fork() to Linux daemon() call.

  If no logging method (-m option) is passed to radvd, and the default
  logging method is used (which is L_STDERR_SYSLOG), then daemon() is
  called with (1, 1) arguments, meaning no chroot (fine) and not closing
  stderr (left there for logging) (not fine). So execute() call that
  spawns radvd and expects it to daemonize and return code never
  actually completes, blocked on stderr.

  The fix is to pass e.g. -m syslog to radvd to make it close stderr and
  return.

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