#385 ✓resolved
Greg Schueler

run -j option fails to find unique job by name

Reported by Greg Schueler | July 12th, 2011 @ 05:29 PM | in Rundeck 1.3 (closed)

the run -j group/name option fails if multiple jobs match the specified job name, even if only one job has the exact job name.


Venkman:test greg$ tools/bin/run -j 'test' 
# No project specified, defaulting to: test
Error: Failed request to run a job: Job not was not unique: /test: 5 jobs found

when rd-jobs lists only a single job with the exact name "test":

Venkman:test greg$ tools/bin/rd-jobs list
# No project specified, defaulting to: test
# Found 6 jobs:
- asdf
- test - 'test update redirect'
- test2 - 'test update redirect'
- uuidmodify test - 'asdf'
- uuidmodify test2 - 'asdffdd'
- uuidmodify test3 - 'asdf'

workaround: determine id via rd-jobs, and use -i option

fix: the RunDeck API needs to allow exact equality query for job name, and the CLI tool needs to use this query filter

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues

Shared Ticket Bins

People watching this ticket