Bug 1536913 - tests/bugs/cli/bug-822830.t fails on Centos 7 and locally
Summary: tests/bugs/cli/bug-822830.t fails on Centos 7 and locally
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1539658 1539699
TreeView+ depends on / blocked
 
Reported: 2018-01-22 03:00 UTC by Nigel Babu
Modified: 2018-03-15 11:25 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1539658 1539699 (view as bug list)
Environment:
Last Closed: 2018-03-15 11:25:40 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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/


Note You need to log in before you can comment on or make changes to this bug.