Bug 814094

Summary:	libvirt starts to require sending keep-alive messages
Product:	Red Hat Enterprise Linux 6	Reporter:	Radek Novacek <rnovacek>
Component:	virt-who	Assignee:	Radek Novacek <rnovacek>
Status:	CLOSED NOTABUG	QA Contact:	Nobody <nobody>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	dyasny, ovasik
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-19 11:58:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.