Project

General

Profile

Actions

Bug #19920

closed

foreman_tasks:cleanup leaves jobs in state "queued"

Added by Adam Ruzicka almost 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Fixed in Releases:
Found in Releases:

Description

[reply] [−] Private Description Beat Rubischon 2017-04-27 08:41:11 EDT
Description of problem:

Jobs are not deleted completely by foreman_tasks:cleanup, the job entry stays in the list in state "queued"

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

Satellite 6.2.8

How reproducible:

always

Steps to Reproduce:
1. run a remote execution job
2. wait 3 days
3. run `foreman-rake foreman_tasks:cleanup TASK_SEARCH="" AFTER=2d --trace`

Actual results:

Jobs are still in the list, without details and in the state "queued"

Expected results:

Jobs are removed completely


Related issues 1 (0 open1 closed)

Related to Foreman Remote Execution - Bug #20025: Job invocations need to be auditedClosedMarek Hulán06/15/2017Actions
Actions #1

Updated by Adam Ruzicka almost 7 years ago

  • Related to Bug #20025: Job invocations need to be audited added
Actions #2

Updated by The Foreman Bot almost 7 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/255 added
Actions #3

Updated by Adam Ruzicka almost 7 years ago

  • Target version changed from 113 to 1.14.1
Actions #4

Updated by Ivan Necas almost 7 years ago

  • Target version changed from 1.14.1 to 1.14.2
Actions #5

Updated by Anonymous almost 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #6

Updated by Ivan Necas almost 7 years ago

  • translation missing: en.field_release set to 279
Actions

Also available in: Atom PDF