RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Spice client is terminated when doing multiple migration of one spice client session. Just do migration from source host to target host and back. When doing the second migration client is closed with message (first migration is successful):
1311704317 INFO [5681:5681] main: Spice client terminated (exitcode = 0)
Migration was done through libvirt and RHEVM3 on RHEL6 host. Once I do migration with the same spice client version on RHEVM2.2 with RHEL5 hosts I am able to do multiple migration (that's why filing bug for spice-server).
After reconnecting with spice client everything is fine => migration itself of guest is successful.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.171
libvirt-0.9.3-7
spice-server-0.8.1-2
spice-client-0.8.0-2

How reproducible:
always

Steps to Reproduce:
1. Connect to a guest using RHEVM3.0 User portal or virsh
2. Keep spice client session.
3. Do migration to another host.
4. Keep spice client session.
5. Do migration back to original host.
  
Actual results:
1311704317 INFO [5681:5681] main: Spice client terminated (exitcode = 0)

Expected results:
No visible changes for user.

Additional info:

Investigation done together with Marian suggests that before the second migration libvirt does not send migrate_info to spice (via qemu-kvm monitor command), so upon migration the server disconnects the client.

Even though I hit it constantly on different setups, Now I am not able to reproduce, but almost all components got updated. I will do some more tests. In case I am not able to reproduce I will close this bug.

Ah, nice additional info, #727969 is a bit similar, but this bug seemed to be different. Given your last comment, maybe it was related to this one.

(In reply to comment #3)
> Ah, nice additional info, #727969 is a bit similar, but this bug seemed to be
> different. Given your last comment, maybe it was related to this one.

I will retest migration with latest components since there were several changes and sort out all those bugs.

I am not able to reproduce on updated components. Closing, will open If I hit that again.