Issue #2768

Updated by bizhang almost 7 years ago

When a task is kicked off I would expect it to populate the worker foreign key when the task is ran [0] 

 I would expect this to be updated in the apply_async function [1].  
 Tasks [1], and I would expect this to be updated for tasks kicked off with apply_async should and apply_async_with_reservations. 

 <pre>TaskStatus.objects.create</pre> will probably have the worker field populated upon creation. 
 Tasks kicked off with to be refactored    to <pre>TaskStatus.objects.update_or_create</pre> to update apply_async_with_reservations would have the worker field updated tasks when it gets they are routed to the worker. worker [2] 

 For reference pulp2 updates the field here [2]