** 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. + + Note that since the 'network.target' dependency is essentially a race + condition between knockd.service executing and the interface it listens + on being configured, it may be necessary to have a more complex network + configuration (which takes longer to fully set up) to more easily + trigger this, such as setting up a bridge or bond with multiple + interfaces and using dhcp and configuring knockd to listen on the bridge + or bond interface. [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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819345 Title: knockd systemd service uses After=network.target instead of network- online.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1819345/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
