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.
Bug 1352799 - Client information from hmp doesn't vanish after client disconnect when using vnc display
Summary: Client information from hmp doesn't vanish after client disconnect when using...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.3
Hardware: x86_64
OS: All
unspecified
medium
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: Guo, Zhiyi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-05 06:12 UTC by Guo, Zhiyi
Modified: 2016-11-07 21:20 UTC (History)
7 users (show)

Fixed In Version: qemu-kvm-rhev-2.6.0-21.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 21:20:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2673 0 normal SHIPPED_LIVE qemu-kvm-rhev bug fix and enhancement update 2016-11-08 01:06:13 UTC

Description Guo, Zhiyi 2016-07-05 06:12:26 UTC
Description of problem:
Client info doesn't vanish after client disconnect when using vnc display

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.6.0-11.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Use vnc with cmd: # /usr/libexec/qemu-kvm -vnc :0 -monitor stdio -qmp tcp:localhost:4444,server,nowait

2.Connect vnc display from local:
# vncviewer 127.0.0.1:5900 -Shared &
And query vnc client info from hmp:
{ "execute": "query-vnc" }


3.Establish another connection to vnc display from local:
# vncviewer 127.0.0.1:5900 &
Client from step 2 is disconnected and query vnc client info again from hmp:
{ "execute": "query-vnc" }

Actual results:
After step 3, both vnc clients info can be queried from hmp:
{ "execute": "query-vnc" }
{"return": {"enabled": true, "auth": "none", "family": "ipv4", "clients": [{"family": "ipv4", "service": "57104", "host": "10.66.10.63", "websocket": false}, {"family": "ipv4", "service": "57100", "host": "10.66.10.63", "websocket": false}], "service": "5900", "host": "0.0.0.0"}}



Expected results:
After step 3, only client info from step 3 exists and can be queried from hmp, this should like:
{ "execute": "query-vnc" }
{"return": {"enabled": true, "auth": "none", "family": "ipv4", "clients": [{"family": "ipv4", "service": "57104", "host": "10.66.10.63", "websocket": false}], "service": "5900", "host": "0.0.0.0"}}

Additional info:
Try same steps on qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64, no such issue happen.
After step2, query from hmp:
{ "execute": "query-vnc" }
{"return": {"enabled": true, "auth": "none", "family": "ipv4", "clients": [{"family": "ipv4", "service": "37606", "host": "127.0.0.1", "websocket": false}], "service": "5900", "host": "0.0.0.0"}}

After step 3, query from hmp:
{ "execute": "query-vnc" }
{"return": {"enabled": true, "auth": "none", "family": "ipv4", "clients": [{"family": "ipv4", "service": "37608", "host": "127.0.0.1", "websocket": false}], "service": "5900", "host": "0.0.0.0"}}

Comment 2 Gerd Hoffmann 2016-07-13 10:24:06 UTC
https://patchwork.ozlabs.org/patch/647832/

Comment 3 Gerd Hoffmann 2016-08-11 13:15:01 UTC
patch posted.  scratch build:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11556331

Comment 4 Miroslav Rezanina 2016-08-16 11:23:01 UTC
Fix included in qemu-kvm-rhev-2.6.0-21.el7

Comment 6 Guo, Zhiyi 2016-09-14 08:06:19 UTC
Verified with qemu-kvm-rhev-2.6.0-25.el7.x86_64, after step 3, only latest vnc connection information remain:

1st vnc connect:
{ "execute": "query-vnc" }
{"return": {"enabled": true, "auth": "none", "family": "ipv4", "clients": [{"family": "ipv4", "service": "40886", "host": "127.0.0.1", "websocket": false}], "service": "5900", "host": "0.0.0.0"}}

2nd vnc connect:
1st vnc client dropped:
{"timestamp": {"seconds": 1473839969, "microseconds": 596}, "event": "VNC_DISCONNECTED", "data": {"server": {"auth": "none", "family": "ipv4", "service": "5900", "host": "0.0.0.0", "websocket": false}, "client": {"family": "ipv4", "service": "40886", "host": "127.0.0.1", "websocket": false}}}

vnc connection remain:
{ "execute": "query-vnc" }
{"return": {"enabled": true, "auth": "none", "family": "ipv4", "clients": [{"family": "ipv4", "service": "40890", "host": "127.0.0.1", "websocket": false}], "service": "5900", "host": "0.0.0.0"}}

Comment 7 Guo, Zhiyi 2016-09-14 08:07:14 UTC
Move to verified per comment 6

Comment 9 errata-xmlrpc 2016-11-07 21:20:54 UTC
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://rhn.redhat.com/errata/RHBA-2016-2673.html


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