Actions
Refactor #32960
closedAsync proxy batch triggering
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman plugin
Target version:
Difficulty:
Triaged:
Yes
Pull request:
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.
Updated by Adam Ruzicka over 3 years ago
- Related to Bug #32961: Proxy side support for async proxy batch triggering added
Updated by The Foreman Bot over 3 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/641 added
Updated by Adam Ruzicka over 3 years ago
- Target version set to foreman-tasks-5.2.0
Updated by The Foreman Bot about 3 years ago
- Fixed in Releases foreman-tasks-5.2.0 added
Updated by Adam Ruzicka about 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset 214342c1598c9ad41f30143c015ec875454279e1.
Updated by Adam Ruzicka about 3 years ago
- Fixed in Releases foreman-tasks-5.3.0 added
- Fixed in Releases deleted (
foreman-tasks-5.2.0)
Actions