Forcing a periodic job with a name similar to other periodic jobs fails to find the job

[jamesooo]

Nomad version

Nomad v1.1.6 (b83d623)

Operating system and Environment details

PRETTY_NAME="Debian GNU/Linux 10 (buster)"

Issue

When a periodic job's name is prepended to other jobs nomad job periodic force is unable to find the job

$ nomad job periodic force cluster-rebalance
Prefix matched multiple periodic jobs

ID                                    Type            Priority  Status   Submit Date
cluster-rebalance                     batch/periodic  50        running  2022-08-15T16:51:47Z
cluster-rebalance-testing-drain       batch/periodic  50        running  2022-08-15T17:38:25Z
cluster-rebalance-testing-validation  batch/periodic  50        running  2022-08-15T17:38:25Z

Reproduction steps

1. create batch/periodic jobs named x, x-testing
2. attempt nomad job periodic force x will now fail with the message Prefix matched multiple periodic jobs

Expected Result

Execution of x should be forced

Actual Result

Command fails to force placement of job and exits with message Prefix matched multiple periodic jobs

Job file (if appropriate)

Nomad Server logs (if appropriate)

Nomad Client logs (if appropriate)

[jrasell]

Hi @jamesooo and thanks for raising this issue which I can also reproduce locally using the steps you provided. The bug is because the CLI performs a prefix search only; whereas we should attempt a direct lookup first before falling back to a prefix lookup.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.