Bug 1974683

Hit following bz on the latest rhel9 (kernel-5.13.0-0.rc4.33.el9.x86_64 & qemu-img-6.0.0-6.el9.x86_64)

+++ This bug was initially created as a clone of Bug #1974366 +++

Description of problem:
The first time set migrate incoming failed due to wrong listening address, then try again, but failed to set the right migrate incoming for 2nd time:
{"execute": "migrate-incoming", "arguments": {"uri": "tcp:10.73.130.69:4000"}, "id": "iyPg3lJW"}
{"id": "iyPg3lJW", "error": {"class": "GenericError", "desc": "duplicate yank instance"}}


Version-Release number of selected component (if applicable):
hosts info: kernel-4.18.0-310.el8.x86_64 & qemu-kvm-6.0.0-19.module+el8.5.0+11385+6e7d542e.x86_64


How reproducible:
100%


Steps to Reproduce:
1.Boot a vm on dst host with "-incoming defer"
2.Set migrate incoming on dst host, will get expected error because it should be $dst_host_ip:
{"execute": "migrate-incoming", "arguments": {"uri": "tcp:$src_host_ip:4000"}, "id": "iyPg3lJW"}
{"timestamp": {"seconds": 1624272064, "microseconds": 65049}, "event": "MIGRATION", "data": {"status": "setup"}}
{"id": "iyPg3lJW", "error": {"class": "GenericError", "desc": "Failed to bind socket: Cannot assign requested address"}}
3.Then try again step 2
{"execute": "migrate-incoming", "arguments": {"uri": "tcp:$dst_host_ip:4000"}, "id": "iyPg3lJW"}
{"id": "iyPg3lJW", "error": {"class": "GenericError", "desc": "duplicate yank instance"}}


Actual results:
Can't succeed setting migrate incoming for the 2nd time after the first time failed


Expected results:
succeed setting migrate incoming for the 2nd time after the first time failed


Additional info:
1.Didn't hit such issue on host(qemu-kvm-4.2.0-52.module+el8.5.0+11386+ef5875dd.x86_64)
2.This issue should be related with yank (Bug 1956897)
3.Didn't reproduce bz on libvirt-daemon-7.4.0-1.module+el8.5.0+11218+83343022.x86_64 since libvirt haven't implemented yank(Bug 1955195)