group.of.nepali.translators team mailing list archive

[Dan Streetman <dan.streetman@xxxxxxxxxxxxx>]

** Changed in: knockd (Ubuntu Trusty)
       Status: New => Invalid

** Changed in: knockd (Ubuntu Xenial)
       Status: New => Invalid

** Changed in: knockd (Ubuntu Bionic)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: knockd (Ubuntu Cosmic)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: knockd (Ubuntu Disco)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: knockd (Ubuntu Disco)
       Status: New => In Progress

** Changed in: knockd (Ubuntu Cosmic)
       Status: New => In Progress

** Changed in: knockd (Ubuntu Bionic)
       Status: New => In Progress

** Changed in: knockd (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: knockd (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: knockd (Ubuntu Bionic)
   Importance: Undecided => Medium

** Description changed:

  [impact]
  
  the knockd systemd service file is configured to start knockd
  After=network.target, however the systemd 'network.target' only means
  network configuration has started, not completed; the interface(s) that
  knockd is configured to listen on may not even be up yet.  In that case,
  starting knockd fails.
  
  [test case]
  
  install, configure, and enable knockd on a system.  reboot the system,
  and check the logs for knockd errors about the interface not being up.
  verify knockd is not running.
  
  [regression potential]
  
  changing the systemd service dependency to use network-online instead of
  network delays when knockd starts, and regressions would be related to
  knockd not running before the network was fully configured, or not
  running at all if systemd failed to ever reach network-online target.
  
  [other info]
  
  this requires the knock systemd service file fix from bug 1799697 also,
  since the knockd systemd service cannot be enabled at all without that
  fix.
+ 
+ this applies only to b/c/d since t/x use upstart for service management,
+ and this bug is only in the knockd systemd service file.

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1819345

Title:
  knockd systemd service uses After=network.target instead of network-
  online.target

Status in knockd package in Ubuntu:
  In Progress
Status in knockd source package in Trusty:
  Invalid
Status in knockd source package in Xenial:
  Invalid
Status in knockd source package in Bionic:
  In Progress
Status in knockd source package in Cosmic:
  In Progress
Status in knockd source package in Disco:
  In Progress

Bug description:
  [impact]

  the knockd systemd service file is configured to start knockd
  After=network.target, however the systemd 'network.target' only means
  network configuration has started, not completed; the interface(s)
  that knockd is configured to listen on may not even be up yet.  In
  that case, starting knockd fails.

  [test case]

  install, configure, and enable knockd on a system.  reboot the system,
  and check the logs for knockd errors about the interface not being up.
  verify knockd is not running.

  [regression potential]

  changing the systemd service dependency to use network-online instead
  of network delays when knockd starts, and regressions would be related
  to knockd not running before the network was fully configured, or not
  running at all if systemd failed to ever reach network-online target.

  [other info]

  this requires the knock systemd service file fix from bug 1799697
  also, since the knockd systemd service cannot be enabled at all
  without that fix.

  this applies only to b/c/d since t/x use upstart for service
  management, and this bug is only in the knockd systemd service file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1819345/+subscriptions