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:
TCP sockets used for initial connection stay in CLOSE_WAIT forever after migration(s). Sockets created during migration are destroyed properly - IOW after increasing number of migrations, you can see set of ports used at initial connection in CLOSED_WAIT state all the time + set of actually active ports

Version-Release number of selected component (if applicable):
spice-gtk-0.20-11.el6.i686

How reproducible:
always

Steps to Reproduce:
1. connect to a VM, look at TCP connection of {virt,remote}-viewer using netstat
2. migrate the VM, look at TCP connections
3. migrate the VM again, look at TCP connections
4. ...

Actual results:
connections that are ESTABLISHED after 1. remain in CLOSED_WAIT in further iterations

Expected results:
only ESTABLISHED connections exist

Additional info:
proxy has no effect on this behaviour

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

fixed in 
http://lists.freedesktop.org/archives/spice-devel/2013-November/015569.html

*** Bug 952375 has been marked as a duplicate of this bug. ***

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.

http://rhn.redhat.com/errata/RHBA-2014-1487.html