Posted downstream.
Note, the easiest case to test that this fixes is:
a) Start qemu on destination
b) Start qemu on source
c) Start migration (migrate -d)
d) Kill qemu on destination before migration finishes
e) do migrate_cancel on source
f) Use 'info migrate' to check the source isn't stuck in cancelling.
You have to be pretty fast to do (d) unless you give the guest lots of RAM.

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/RHEA-2017:3169

Note

You need to
log in
before you can comment on or make changes to this bug.