Issue #2768
Updated by bizhang over 7 years ago
When a task is kicked off I would expect it to populate the worker foreign key [0] when the task is ran [0] I would expect this to be updated in the apply_async function when the Task status object is created [1]. Tasks kicked off with apply_async should have the worker field populated upon creation. Tasks kicked off with apply_async_with_reservations would have the worker field updated when it gets routed to the worker. For reference pulp2 updates the field here [2] [0] https://github.com/pulp/pulp/blob/b3ff9a93bba4af1405f57e907944270b3052668a/platform/pulp/app/models/task.py#L158 https://github.com/pulp/pulp/blob/3.0-dev/platform/pulpcore/app/models/task.py#L158 [1] https://github.com/pulp/pulp/blob/b3ff9a93bba4af1405f57e907944270b3052668a/platform/pulp/tasking/tasks.py#L243 https://github.com/pulp/pulp/blob/3.0-dev/platform/pulpcore/tasking/tasks.py#L243 [2] https://github.com/pulp/pulp/blob/master/server/pulp/server/async/tasks.py#L484