systemd unit name doesn't allow instances ('@controller' or '@worker')

[ataraxia937]

trafficstars

Describe the bug The boundary.service file uses the %i variable, so it's clearly meant to be run as '[email protected]', '[email protected]', and so on.

But systemctl/systemd doesn't understand how to create instances on a unit whose name doesn't end in an '@' sign. So in order to actually use the unit file, I have to copy /usr/lib/systemd/system/boundary.service to /etc/systemd/system/[email protected].

Then I am able to systemctl enable boundary@controller successfully.

Please rename the unit file to [email protected].

To Reproduce Steps to reproduce the behavior:

1. See error on running enable command: # systemctl enable boundary@controller Failed to enable unit: Unit file [email protected] does not exist.

Expected behavior A clear and concise description of what you expected to happen. systemctl should be able to create the instance links.

Additional context I'm running on Amazon Linux 2.