Unable to get job status: Multiple matches found for id "<job_name>"

[pznamensky]

Hi,
We're unable to get job's status if it's name can be part of another job name.
For instance:

~ $ nomad status
ID        Type     Priority  Status   Submit Date
test-job    service  50        running  08/23/17 16:40:12 MSK                                                                                          
test-job1   service  50        running  08/23/17 22:58:17 MSK                                                                                          
test-job10  service  50        running  08/23/17 22:58:13 MSK                                                                                          

~ $ nomad status test-job
Multiple matches found for id "test-job"

~ $ nomad status test-job1
Multiple matches found for id "test-job1"

~ $ nomad status test-job10
ID            = test-job10
Name          = test-job10
Submit Date   = 08/23/17 22:58:13 MSK
Type          = service
Priority      = 50
Datacenters   = staging
Status        = running
Periodic      = false
Parameterized = false

Summary
Task Group  Queued  Starting  Running  Failed  Complete  Lost
test-job      0       0         1        0       0         0

Latest Deployment
ID          = 8e3fea8c
Status      = successful
Description = Deployment completed successfully

Deployed
Task Group  Desired  Placed  Healthy  Unhealthy
test-job      1        1       1        0

Allocations
ID        Node ID   Task Group  Version  Desired  Status   Created At
686bb943  60ad5a4a  test-job      1        run      running  08/26/17 05:49:23 MSK

Nomad version

Nomad v0.7.0-dev (6fb08b8)

[dsolsona]

I can reproduce this with Nomad 0.6.2, it is not possible to get the status of a job if you have multiple jobs that have the same prefix.

This works fine in Nomad 0.6.0

[pznamensky]

Yes, nomad job status <job_name> works fine.

[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.