The logs should contain information about the state change of a task, including task_id, execution plan id, new state and result (for paused and stopped tasks), for example: <pre> 2019-04-16T14:22:10 [I|bac|] Task {label: Actions::Try::Pause, id: 759dfb3d-f14a-4112-b336-e6f65e3e5eb9, execution_plan_id: 75d6e6fc-bc18-4e60-8d34-5a5a7d5dccb0} state changed: planning 2019-04-16T14:22:10 [I|bac|] Task {label: Actions::Try::Pause, id: 759dfb3d-f14a-4112-b336-e6f65e3e5eb9, execution_plan_id: 75d6e6fc-bc18-4e60-8d34-5a5a7d5dccb0} state changed: planned 2019-04-16T14:22:10 [I|bac|] Task {label: Actions::Try::Pause, id: 759dfb3d-f14a-4112-b336-e6f65e3e5eb9, execution_plan_id: 75d6e6fc-bc18-4e60-8d34-5a5a7d5dccb0} state changed: running 2019-04-16T14:22:10 [I|bac|] Task {label: Actions::Try::Pause, id: 759dfb3d-f14a-4112-b336-e6f65e3e5eb9, execution_plan_id: 75d6e6fc-bc18-4e60-8d34-5a5a7d5dccb0} state changed: paused result: error </pre>
Created from redmine issue https://projects.theforeman.org/issues/26626
Upstream bug assigned to inecas
Verified on Sat 6.6 snap 8, task state changes are now part of production log
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3172