Project

General

Profile

Actions

Bug #19937

closed

it is hard (or there is no way at all) to cancel pending tasks from old remote execution job

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

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

Description of problem:
It is hard (or there is no way at all) to cancel pending tasks from old remote execution job.

Version-Release number of selected component (if applicable):
satellite-6.2.8-4.0.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Have clients managed by capsule
2. Start ReX job on the clients and white (some of) them are in pending,
stop capsule
3. Now lets say we have just removed that capsule for good so we want to
finish all the pending tasks from Satellite

Actual results:
You have to go to job -> Job Task -> Sub tasks, select one by one and click "Cancel". I have not found anything in Hammer or in API. Master task have "Cancel" button inactive. Dynflow console does not have "cancel" or "skip" links.

Expected results:
There should be a way (ideally in all webUI, API and hammer) to cancel tasks of a given job (you can say this via task search query "parent_task_id = ...").

Additional info:
This is error I see in the child task before clicking "Cancel":

Error loading data from Capsule: RestClient::ResourceNotFound - 404 Resource Not Found

When I click "Cancel", this appears and after some time 3 more messages appears and then finally child task is completed:

Initialization error: RestClient::InternalServerError - 500 Internal Server Error


Related issues 4 (0 open4 closed)

Related to foreman-tasks - Bug #20300: Need better support for cancelling proxy tasksClosedAdam Ruzicka07/13/2017Actions
Related to Foreman Remote Execution - Feature #20496: Expose job invocation cancelling via hammerClosedAdam Ruzicka08/03/2017Actions
Has duplicate Foreman Remote Execution - Bug #18569: Remote execution jobs in state queued, unable to proceed or cancelDuplicate02/20/2017Actions
Blocked by Foreman Remote Execution - Refactor #20466: Use the polling sub plans functionality in RunHostsJobClosedAdam Ruzicka08/01/2017Actions
Actions #1

Updated by Adam Ruzicka almost 7 years ago

  • Target version set to 113

The batch planning should help with this a bit, but we still need to provide a reliable way of cancelling sub-tasks which were already planned and are pending.

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/263 added
Actions #3

Updated by Adam Ruzicka almost 7 years ago

  • Related to Bug #20300: Need better support for cancelling proxy tasks added
Actions #4

Updated by Adam Ruzicka over 6 years ago

  • Blocked by Refactor #20466: Use the polling sub plans functionality in RunHostsJob added
Actions #5

Updated by Ivan Necas over 6 years ago

  • Related to Feature #20496: Expose job invocation cancelling via hammer added
Actions #6

Updated by Anonymous over 6 years ago

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

Updated by Ivan Necas over 6 years ago

  • Has duplicate Bug #18569: Remote execution jobs in state queued, unable to proceed or cancel added
Actions #8

Updated by Ivan Necas over 6 years ago

  • translation missing: en.field_release set to 292
Actions

Also available in: Atom PDF