Bug 1559829

Summary:	snap/gcron.py: ABRT report for package glusterfs has reached 100 occurrences
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	snapshot	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.12	CC:	amarts, amukherj, bugs, ndevos
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.11	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 14:11:29 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:	1590193
Bug Blocks:

Description Kaleb KEITHLEY 2018-03-23 11:24:07 UTC

Description of problem:

see https://retrace.fedoraproject.org/faf/reports/bthash/1ed1a110b97400a32634f92226301f0e2ef470ac/

(And yes, it does seem strange that we're getting Fedora ABRT reports from a CentOS box. Maybe CentOS ABRTs get sent to Fedora?)



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Kaleb KEITHLEY 2018-04-02 15:21:40 UTC

100 occurances

Comment 2 Niels de Vos 2018-06-12 08:09:39 UTC

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

Comment 3 Worker Ant 2018-06-18 07:31:49 UTC

REVIEW: https://review.gluster.org/20301 (gcron: create the lockfile if it is missing) posted (#1) for review on release-3.12 by Niels de Vos

Comment 4 Worker Ant 2018-06-18 13:21:01 UTC

REVIEW: https://review.gluster.org/20306 (gcron: catch OSError as well as IOError) posted (#1) for review on release-3.12 by Niels de Vos

Comment 5 Worker Ant 2018-06-25 13:43:08 UTC

COMMIT: https://review.gluster.org/20306 committed in release-3.12 by "Niels de Vos" <ndevos> with a commit message- gcron: catch OSError as well as IOError

In case os.open() fails because the file does not exist, an OSError is
raised. To prevent the script to abort uncleanly, catch the OSError in
addition to the IOError.

Change-Id: I48e5b23e17d63639cc33db51b4229249a9887880
Fixes: bz#1559829
Signed-off-by: Niels de Vos <ndevos>
(cherry picked from commit 26b52694feb04c98e6c9436bcd4e23e1687f0237)

Comment 6 Worker Ant 2018-06-25 13:43:27 UTC

COMMIT: https://review.gluster.org/20301 committed in release-3.12 by "Shyamsundar Ranganathan" <srangana> with a commit message- gcron: create the lockfile if it is missing

The lockfile for the job may not exist yet. If that is the case, it
should be created upon the first time it is accessed.

Change-Id: I4da2b3ecdb79cc63ed82cc7bfa026c8f08d4d043
Fixes: bz#1559829
Signed-off-by: Niels de Vos <ndevos>
(cherry picked from commit 7005b1a336e483ec150c2f924a618dcfe197db0b)

Comment 7 Shyamsundar 2018-10-23 14:11:29 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.12.11, please open a new bug report.

glusterfs-3.12.11 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-July/000104.html
[2] https://www.gluster.org/pipermail/gluster-users/