Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1597805

Summary: Stale lock with lk-owner all-zeros is observed in some tests
Product: [Community] GlusterFS Reporter: Pranith Kumar K <pkarampu>
Component: replicateAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1598193 (view as bug list) Environment:
Last Closed: 2018-10-23 15:13:25 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: 1598193    

Description Pranith Kumar K 2018-07-03 16:10:48 UTC
Description of problem:
    Problem:
    In the new eager-lock implementation lk-owner is assigned after the
    'local' is added to the eager-lock list, so there exists a possibility
    of lock being sent even before lk-owner is assigned.
    
    Fix:
    Make sure to assign lk-owner before adding local to eager-lock list


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-07-03 16:23:10 UTC
REVIEW: https://review.gluster.org/20455 (cluster/afr: Make sure lk-owner is assigned at the time of lock) posted (#1) for review on master by Pranith Kumar Karampuri

Comment 2 Worker Ant 2018-07-04 14:39:05 UTC
COMMIT: https://review.gluster.org/20455 committed in master by "Pranith Kumar Karampuri" <pkarampu> with a commit message- cluster/afr: Make sure lk-owner is assigned at the time of lock

Problem:
In the new eager-lock implementation lk-owner is assigned after the
'local' is added to the eager-lock list, so there exists a possibility
of lock being sent even before lk-owner is assigned.

Fix:
Make sure to assign lk-owner before adding local to eager-lock list

fixes bz#1597805
Change-Id: I26d1b7bcf3e8b22531f1dc0b952cae2d92889ef2
Signed-off-by: Pranith Kumar K <pkarampu>

Comment 3 Shyamsundar 2018-10-23 15:13:25 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-5.0, please open a new bug report.

glusterfs-5.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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/