Bug 1536913

Summary:	tests/bugs/cli/bug-822830.t fails on Centos 7 and locally
Product:	[Community] GlusterFS	Reporter:	Nigel Babu <nigelb>
Component:	cli	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nbalacha
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1539658 1539699 (view as bug list)		Environment:
Last Closed:	2018-03-15 11:25:40 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:
Bug Blocks:	1539658, 1539699

Description Nigel Babu 2018-01-22 03:00:18 UTC

This test fails because we don't reset errno to 0 before the strtol call. When it fails, it fails because errno = 101.

https://github.com/gluster/glusterfs/blob/master/libglusterfs/src/common-utils.c#L2441

Comment 1 Worker Ant 2018-01-22 03:08:59 UTC

REVIEW: https://review.gluster.org/19262 (libglusterfs: Reset errno before call) posted (#1) for review on master by Nigel Babu

Comment 2 Worker Ant 2018-01-23 18:08:58 UTC

COMMIT: https://review.gluster.org/19262 committed in master by \"Nigel Babu\" <nigelb> with a commit message- libglusterfs: Reset errno before call

This was causing Gluster to return a failure when testing on Centos7.

BUG: 1536913
Change-Id: Idb90baef05058123a7f69e94a51dd79abd371815
Signed-off-by: Nigel Babu <nigelb>

Comment 3 Shyamsundar 2018-03-15 11:25:40 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-4.0.0, please open a new bug report.

glusterfs-4.0.0 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] http://lists.gluster.org/pipermail/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/