Project

General

Custom queries

Profile

Actions
Copy link

Bug #24930

closed

hammer job-invocation output returns ISE on providing invalid invocation id

Added by Adam Ruzicka over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Adam Ruzicka
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
1628561
Pull request:
https://github.com/theforeman/foreman_remote_execution/pull/378
Fixed in Releases:
foreman_remote_execution 1.6.4 (Foreman 1.20)
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1628561

Description of problem:
when passing wrong-non-existing job-invocation id to the `output` subcommand (together with a valid host parameter), the server returns ISE (err 500) - NoMethodError: undefined method `task' for nil:NilClass

instead of a proper 404 response code

How reproducible:
always

Steps to Reproduce:
1. have some valid host (Say: foo)
2. hammer job-invocation output --id <invalid-id> --host foo

Actual results:
internal server error returned

Expected results:
404 status codereturned from server

Additional info:

Actions
Copy link
 #1

Updated by The Foreman Bot over 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Adam Ruzicka
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/378 added
Actions
Copy link
 #2

Updated by Anonymous over 6 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #3

Updated by Ivan Necas over 6 years ago

  • Subject changed from hammer job-invocation output returns ISE on providing invalid invocation id to hammer job-invocation output returns ISE on providing invalid invocation id
  • Fixed in Releases foreman_remote_execution 1.6.4 (Foreman 1.20) added
Actions
Copy link

Also available in: Atom PDF