uploaded for b/f/g, thanks!

** Description changed:

  [impact]
  
  knockd doesn't correctly start at boot
  
  [test case]
  
- TBD
+ install a test system; linux mint (from comment 5) or plain ubuntu
+ 
+ check if any installed-by-default services pull in network-
+ online.target:
+ 
+ $ systemctl list-dependencies --reverse network-online.target
+ network-online.target
+ 
+ if any services are listed as reverse deps, disable or uninstall them;
+ for example, with the default lxd container image:
+ 
+ ubuntu@lp1912826-f:~$ systemctl list-dependencies --reverse 
network-online.target
+ network-online.target
+ ● ├─cloud-config.service
+ ● ├─cloud-final.service
+ ● ├─iscsid.service
+ ● └─open-iscsi.service
+ 
+ so those services need to be disabled, or the packages uninstalled, so
+ there are no services that Want=network-online.target.
+ 
+ Then install knockd and configure (see comment 5) and reboot, and
+ confirm that knockd is started (and fails) before networking starts.
+ Also check that network-online.target is still unwanted, and thus not
+ started, so knockd isn't delayed until after the network is up.
  
  [regression potential]
  
  any regression would likely cause knockd to fail to correctly start;
  regressions after starting up are unlikely.
  
  [scope]
  
  this is needed in b/f/g/h
  
  [other info]
  
  note that this project seems essentially dead upstream, the last official 
release was 2014:
  https://www.zeroflux.org/projects/knock
  
  [original description]
  
  I would like to request a small fix in the systemd unit file
  knockd.service. Please add the [Unit] line
  
  Wants=network-online.target
  
  Bug description:
  When the system starts, the knockd daemon fails with a message "knockd[1012]: 
could not open eno1: eno1: That device is not up". This bug was also described 
here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1730634
  
  In accordance with the recommendations in the systemd.unit
  documentation, it should be sufficient to accompany the After= option
  with a Wants= option.
  
  This fixed the issue for me; and in the syslog I could see that the
  network manager comes online before the knockd daemon (as required),
  instead of after.
  
  Tested on Linux Mint 20.1 that is based on Ubuntu focal (knockd
  0.7-1ubuntu3).

** Changed in: knockd (Ubuntu Groovy)
       Status: Incomplete => In Progress

** Changed in: knockd (Ubuntu Focal)
       Status: Incomplete => In Progress

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

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912826

Title:
  Knockd service fails to start due to missing dependency

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to