Bug 808584

Summary:	outOfProcess operations time out with abrt-addon-python installed
Product:	[Retired] oVirt	Reporter:	Adam Litke <alitke>
Component:	vdsm	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	abaron, acathrow, bazulay, iheim, jkt, lpeer, smizrahi
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-22 00:42:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	808562, 837333
Bug Blocks:	799722

Description Adam Litke 2012-03-30 18:59:46 UTC

Description of problem:

On a Fedora 16 host with the abrt-addon-python package installed, vsdm can enter a state where outOfProcess operations do not complete.  This can cause many different errors (including failure to initialize storage if this machine is also SPM).

Version-Release number of selected component (if applicable):
vdsm-4.9.6-0.2.git
abrt-addon-python-2.0.7-2.fc16

How reproducible:

A freshly installed vdsm may not exhibit the problem even with the abrt python hook present.  For me, completing a few cycles of: install rpm, start vdsm, stop vdsm, remove rpm, repeat -- will cause the symptoms to appear.

Steps to Reproduce:
1. install vdsm and abrt-addon-python
2. complete several vdsm reinstall/restart cycles until ovirt-engine is unable to initialize storage
  
Actual results:

Vdsm is unable to locate and connect the master storage domain.

Expected results:

No errors are reported.

Additional info:

The problem can be worked around by removing abrt-addon-python from the system and restarting vdsm.

Comment 1 Dan Kenigsberg 2012-04-07 19:07:11 UTC

This is clearly very odd. I have abrt-addon-python-2.0.7-2.fc16.x86_64 and vdsm installed on my f16, with vdsm doing gazillion installation cycles, and I have never see this.

When it occurs, does it happen repeatedly? Does *all* oop fail? Could you attach a gdb stack of vdsm at this condition? Does `tests/run_tests.sh processPoolTests.py` reproduce any of it?

Comment 2 Dan Kenigsberg 2012-04-09 08:35:08 UTC

Oh, does removal of oop logging makes the issue disappear?
http://gerrit.ovirt.org/2532

Comment 3 Dan Kenigsberg 2012-04-18 20:46:52 UTC

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

Comment 4 Dan Kenigsberg 2013-09-22 00:42:54 UTC

Bug solved on the abrt side with bug 837333.