This is related to https://github.com/systemd/systemd/issues/661
** Bug watch added: github.com/systemd/systemd/issues #661 https://github.com/systemd/systemd/issues/661 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1808432 Title: systemctl template units not enabled per docs Status in systemd package in Ubuntu: New Bug description: Report is for Description: Ubuntu 16.04.4 LTS Release: 16.04 Package data is Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign No log file is applicable The problem is that systemctl enable does not perform according to documentation in enabling template unit files. If a template unit file exists /full_path_to/tmpl@.service and you try to enable it with systemctl per the docs sudo systemctl enable /full_path_to/tmpl@instance.service or systemctl --user enable /full_path_to/tmpl@instance.service you get the error Failed to execute operation: No such file or directory What should happen is that systemctl fails to find /full_path_to/tmpl@instance.service so it then tries the template name /full_path_to/tmpl@.service, finds it, and creates a symlink to that template file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp