fleetctl start for unitfile shows wrong error

[zeisss]

fleetctl start supports submit a local file when a unit with the name does not exist in fleet. If the unit contains an @ it can be scheduled multiple times with different values. If a file with that name exists, it cannot be used, but must be moved to a filename with anything behind the @.

core@core-01 ~$ ls
api@1.service
core@core-01 ~ $ fleetctl start api@1
Error creating units: unable to find Unit(api@1.service) or template Unit(api@.service) in Registry or on filesystem
core@core-01 ~ $ mv api@1.service api@.service
core@core-01 ~ $ fleetctl start api@1
Unit api@1.service launched on 304e333b.../172.17.8.102
core@core-01 ~ $ fleetctl -version
fleetctl version 0.8.3

Expected behavior:
Either being able to add a file with the name api@1.service or not showing that name in the error message (that it couldn't be found).

[bcwaldon]

@zeisss What happens if you try to fleetctl start api@1.service with a local api@1.service rather than fleetctl start api@1?

[zeisss]

The full qualified filename (fleetctl start api@1.service) does indeed work.

[bcwaldon]

@zeisss Found the bug here: #1050