Bug 1084485 - tests/bugs/bug-963678.t is crashing in Rackspace, generating core file
Summary: tests/bugs/bug-963678.t is crashing in Rackspace, generating core file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Brian Foster
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-04 12:58 UTC by Justin Clift
Modified: 2015-07-13 04:35 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-11 08:29:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Justin Clift 2014-04-04 12:58:25 UTC
Description of problem:

  tests/bugs/bug-963678.t is crashing when run in Rackspace, generating
  a core file every time.

  With some added echo statements, to show the commands being run, this
  is what we see:

    # tests/bugs/bug-963678.t 
    mkdir: cannot create directory `/mnt/glusterfs/0': File exists
    1..18
    TEST glusterd
    ok 1
    TEST gluster --mode=script --wignore volume create patchy replica 2 jc-api-test-node0.cloud.gluster.org:/d/backends/patchy1 jc-api-test-node0.cloud.gluster.org:/d/backends/patchy2
    ok 2
    TEST gluster --mode=script --wignore volume start patchy
    ok 3
    TEST glusterfs --volfile-id=patchy --volfile-server=jc-api-test-node0.cloud.gluster.org /mnt/glusterfs/0 --attribute-timeout=0 --entry-timeout=0
    ok 4
    require_fallocate -l 1m /mnt/glusterfs/0/file
    require_fallocate -p -l 512k /mnt/glusterfs/0/file
    rm: cannot remove `/mnt/glusterfs/0/file': Transport endpoint is not connected
    TEST fallocate -l 1m /mnt/glusterfs/0/file
    fallocate: /mnt/glusterfs/0/file: open failed: Transport endpoint is not connected
    not ok 5 
    stat: cannot stat `/mnt/glusterfs/0/file': Transport endpoint is not connected
    blksz=
    stat: cannot stat `/mnt/glusterfs/0/file': Transport endpoint is not connected
    stat: cannot stat `/mnt/glusterfs/0/file': Transport endpoint is not connected
    nblks=
    stat: cannot stat `/mnt/glusterfs/0/file': Transport endpoint is not connected
    tests/bugs/bug-963678.t: line 45: * : syntax error: operand expected (error token is "* ")
    tests/bugs/bug-963678.t: line 46: * : syntax error: operand expected (error token is "* ")
    (I have an exit statement embedded after this, so the test stops)

  It's leaving a core file in root.

  Brian Foster, author of the test, has investigated and created a
  1-liner fix which I'll submit to Gerrit in a few minutes. :)


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

  Upstream git master as of Fri 4th Apr 2014
  commit 997c89b6172116557f981510a94232486ec526b0


How reproducible:

  Every time


Steps to Reproduce:
1. # cd glusterfs
2. # tests/bugs/bug-963678.t

   Problem happens here

Comment 1 Anand Avati 2014-04-04 13:04:32 UTC
REVIEW: http://review.gluster.org/7402 (afr: Simple 1-liner fix for crash in Rackspace) posted (#1) for review on master by Justin Clift (justin)

Comment 2 Anand Avati 2014-04-04 16:49:15 UTC
COMMIT: http://review.gluster.org/7402 committed in master by Anand Avati (avati) 
------
commit 50b33f4050e11876ecb8e3512880334de25e3f21
Author: Brian Foster <bfoster>
Date:   Fri Apr 4 12:59:58 2014 +0000

    afr: Simple 1-liner fix for crash in Rackspace
    
    BUG: 1084485
    Change-Id: I89ddf10add041638ef70baebbce0ec2807ef4b6d
    Signed-off-by: Justin Clift <justin>
    Reviewed-on: http://review.gluster.org/7402
    Reviewed-by: Anand Avati <avati>

Comment 3 Anand Avati 2014-04-07 05:01:07 UTC
REVIEW: http://review.gluster.org/7407 (cluster/afr: Init local on txn-frame for zerofill) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 4 Anand Avati 2014-04-08 18:21:00 UTC
COMMIT: http://review.gluster.org/7407 committed in master by Anand Avati (avati) 
------
commit 5216e53dedcb74079aaeaec65a2af9486690fea6
Author: Pranith Kumar K <pkarampu>
Date:   Mon Apr 7 10:19:37 2014 +0530

    cluster/afr: Init local on txn-frame for zerofill
    
    Change-Id: I516f4fb0237dd0b3e512117bf987cea69f8678b8
    BUG: 1084485
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/7407
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Brian Foster <bfoster>
    Reviewed-by: Anand Avati <avati>

Comment 5 Niels de Vos 2014-09-22 12:37:33 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 6 Niels de Vos 2014-11-11 08:29:30 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


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