Bug 1126354

Summary:	dist-geo-rep: Python backtrace seen in geo-rep logs "ValueError: signal only works in main thread"
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vikhyat Umrao <vumrao>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED ERRATA	QA Contact:	Sudhir D <sdharane>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	2.1	CC:	aavati, asrivast, avishwan, bbandari, csaba, fdacunha, fharshav, nlevinki, nsathyan, pmutha, psriniva, sdharane, ssamanta, vbhat, vgaikwad, vshankar, vumrao
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 2.1.4
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.65rhs-1	Doc Type:	Bug Fix
Doc Text:	Previously, Geo-replication monitor would terminate abruptly and the Red Hat Storage node would not sync with the other nodes due to a a limitation in Python. This limited the code to handle the signals only in the main thread. With this fix, the Geo-replication worker thread shuts down gracefully and the Geo-replication monitor does not terminate abruptly.	Story Points:	---
Clone Of:	1044420	Environment:
Last Closed:	2014-09-18 18:24:01 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:
Embargoed:
Bug Depends On:	1044420
Bug Blocks:	1073815, 1078068

Comment 3 M S Vishwanath Bhat 2014-08-18 19:31:55 UTC

I used to hit this very consistently during automation run in beaker. Now I run the same thing once more and it is not happenning.

https://beaker.engineering.redhat.com/jobs/724504

Tested in version: glusterfs-3.4.0.65rhs

Comment 4 Pavithra 2014-08-22 05:30:27 UTC

Hi Aravinda,

Please review the edited doc text for technical accuracy and sign off.

Comment 5 Aravinda VK 2014-08-22 06:39:50 UTC

doc text looks good to me.

Comment 7 errata-xmlrpc 2014-09-18 18:24:01 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.

http://rhn.redhat.com/errata/RHSA-2014-1263.html