Bug 814094 - libvirt starts to require sending keep-alive messages
Summary: libvirt starts to require sending keep-alive messages
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-who
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-19 08:37 UTC by Radek Novacek
Modified: 2016-12-01 00:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-19 11:58:00 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Radek Novacek 2012-04-19 08:37:49 UTC 
libvirt has been rebased in RHEL 6.3 and now it requires to send keep-alive messages. Virt-who doesn't send them (and probably won't in the future because it would mean to implement event loop), so the connection get closed between two messages, so virt-who is getting "Broken pipe" error.

Disabling keep-alive messages is not possible now because of bug #813819.

Virt-who internal mechanism retries the connection to libvirt after the failure and it succeeds, so this mean no harm, just some unnecessary operations. And it breaks waiting for events from libvirt.
Comment 2 Radek Novacek 2012-04-19 11:58:00 UTC 
This is bug in invalid. This issue was caused by implementing double-forking in bug #806225. The event loop for interacting with libvirt was created to soon (before the double-fork) and keep-alive messages gets lost somehow. Will be fixed as part of fix in bug #813299, because it's same part of the code.

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