Project

General

Profile

Actions

Feature #21358

closed

Cancelled future/recurring job invocations should not get the status "failed" but rather "cancelled"

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

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-

Description

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

Description of problem:

When scheduling a job for execution in the future, it gets the status "queued". If you go to the job and press "Cancel job", the job gets status "failed" the task will contain a huge error output. This is not a good user experience.

Version-Release number of selected component (if applicable):
6.2.12

How reproducible:
Always

Steps to Reproduce:
1. Go to Hosts -> Job templates
2. Choose a Job template, e.g. "Run Command - SSH Default", and click "Run" at the right hand side
3. Enter a Search query, e.g "name = test.example.com"
4. Enter a command to execute, e.g. "whoami"
5. Click on "Schedule future execution" and enter a date in the future, e.g. an hour later
6. Click Submit
7. Go to Monitor -> Jobs
8. Notice that the new job has status "queued"
9. Click on the job name, in this case "Run whoami"
10. Click on "Cancel Job"
11. Click on "Job Task" and notice that "State: stopped" and "Result: error" and the long error message
12. Go back to Monitor -> Jobs and notice that the job status is now "failed"

Actual results:
Job status is "failed" with a huge error message in the task.

Expected results:
Job status should be "cancelled" and the error message should not clutter the job task.

Additional info:
It would be a much better user experience if the there is another status called "cancelled". This would allow users to separate tasks that have actually failed because of something not working properly and jobs that are cancelled manually.

Actions #1

Updated by Adam Ruzicka over 6 years ago

  • Target version set to 113

There's a fair chance this will need to touch foreman-tasks and/or dynflow code. Leaving it at the rex project for now.

Actions #2

Updated by The Foreman Bot about 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Anonymous
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/307 added
Actions #3

Updated by The Foreman Bot about 4 years ago

  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/482 added
Actions #4

Updated by The Foreman Bot almost 4 years ago

  • Fixed in Releases added
Actions #5

Updated by Anonymous almost 4 years ago

  • Status changed from Ready For Testing to Closed
Actions #6

Updated by Adam Ruzicka almost 4 years ago

  • Triaged set to No
  • Fixed in Releases foreman_remote_execution 3.2.0 added
  • Fixed in Releases deleted ()
Actions

Also available in: Atom PDF