On Fri, Mar 19, 2021 at 10:42:25PM +0100, Jiri Denemark wrote:
> In case an async job spans multiple APIs (e.g., incoming migration) the
> API that started the job is recorded as the asyncOwnerAPI even though it
> is no longer running and the owner thread is updated properly to the one
> currently handling the job. Let's also update asyncOwnerAPI to make it
> more obvious which is the current (or the most recent) API involved in
> the job.
>
> Signed-off-by: Jiri Denemark <jdene...@redhat.com>
> ---
Reviewed-by: Erik Skultety <eskul...@redhat.com>
