Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Trying to start a non-existant job should return an error #562

Closed
godber opened this issue Sep 21, 2017 · 0 comments
Closed

Trying to start a non-existant job should return an error #562

godber opened this issue Sep 21, 2017 · 0 comments
Labels
bug priority:medium

Comments

@godber
Copy link
Member

godber commented Sep 21, 2017

Teraslice should return an error when trying to start a job for a non-existent job_id.

For example, when I tried to restart f443e789-b7f0-4a82-a74c-c79514beee75 I accidentally omitted the leading f and ran this instead:

curl -XPOST -sS ts_test1.tera4:5678/jobs/443e789-b7f0-4a82-a74c-c79514beee75/_start

Teraslice did not respond at all, it just immediately returned.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug priority:medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@godber @kstaken