Bug #32047
closed
Matching tasks using various fields when getting proxy action outputs on demand
Added by Adam Ruzicka almost 4 years ago.
Updated over 3 years ago.
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.
Related issues
1 (1 open — 0 closed)
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/617 added
- Related to Bug #32049: Foreman sends unnecessary data to the smart proxy when running REX jobs added
- Fixed in Releases foreman-tasks-4.1.0 added
- Status changed from Ready For Testing to Closed
- Target version set to foreman-tasks-4.1.0
- Pull request https://github.com/theforeman/foreman-tasks/pull/629 added
- 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)
- Fixed in Releases foreman-tasks-core-0.3.6 added
Also available in: Atom
PDF
Updated by 
Updated by