Project

General

Profile

Actions

Refactor #32960

closed

Async proxy batch triggering

Added by Adam Ruzicka almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman plugin
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

When triggering tasks on the smart proxy before batch triggering, we always got back the uuid of the task on the smart proxy. With batch triggering this stayed the same, but we had to wait until all the tasks in the batch were planned, which could take some time.

Instead of waiting for the uuids, we make the proxy-side tasks be spawned with uuids matching the ones on foreman's side and therefore we don't have to wait for them to be fully planned.


Related issues 1 (0 open1 closed)

Related to foreman-tasks - Bug #32961: Proxy side support for async proxy batch triggeringClosedAdam RuzickaActions
Actions #1

Updated by Adam Ruzicka almost 3 years ago

  • Related to Bug #32961: Proxy side support for async proxy batch triggering added
Actions #2

Updated by The Foreman Bot almost 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-tasks/pull/641 added
Actions #3

Updated by Adam Ruzicka over 2 years ago

  • Target version set to foreman-tasks-5.2.0
Actions #4

Updated by Adam Ruzicka over 2 years ago

  • Triaged changed from No to Yes
Actions #5

Updated by The Foreman Bot over 2 years ago

  • Fixed in Releases foreman-tasks-5.2.0 added
Actions #6

Updated by Adam Ruzicka over 2 years ago

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

Updated by Adam Ruzicka over 2 years ago

  • Fixed in Releases foreman-tasks-5.3.0 added
  • Fixed in Releases deleted (foreman-tasks-5.2.0)
Actions

Also available in: Atom PDF