Actions
Bug #32047
closed
Matching tasks using various fields when getting proxy action outputs on demand
Difficulty:
Triaged:
No
Description
When we're retrieving outputs of proxy actions we get back a serialized execution plan, walk its actions and look for an action with either expected action_class or operation name. This is somewhat flaky.
Updated by The Foreman Bot almost 4 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/617 added
Updated by Adam Ruzicka almost 4 years ago
- Related to Bug #32049: Foreman sends unnecessary data to the smart proxy when running REX jobs added
Updated by The Foreman Bot almost 4 years ago
- Fixed in Releases foreman-tasks-4.1.0 added
Updated by Adam Ruzicka almost 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset cd69cd6b3a6a6652f77706e96a44cd1e732be85f.
Updated by Adam Ruzicka almost 4 years ago
- Target version set to foreman-tasks-4.1.0
Updated by The Foreman Bot over 3 years ago
- Pull request https://github.com/theforeman/foreman-tasks/pull/629 added
Updated by Adam Ruzicka over 3 years ago
- Target version changed from foreman-tasks-4.1.0 to foreman-tasks-4.1.1
- Fixed in Releases foreman-tasks-4.1.1 added
- Fixed in Releases deleted (
foreman-tasks-4.1.0)
Updated by Adam Ruzicka over 3 years ago
- Fixed in Releases foreman-tasks-core-0.3.6 added
Actions