Bug 1644474 - afr/lease: Read child nodes from lease structure
Summary: afr/lease: Read child nodes from lease structure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-31 00:30 UTC by Shyamsundar
Modified: 2018-11-29 15:26 UTC (History)
1 user (show)

Fixed In Version: glusterfs-4.1.6
Clone Of:
Environment:
Last Closed: 2018-11-29 15:26:07 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 21495 0 None Merged afr/lease: Read child nodes from lease structure 2018-10-31 14:19:34 UTC

Description Shyamsundar 2018-10-31 00:30:22 UTC
For lease operation, we allocate and store child nodes
data in lease structure. Use the same in afr_lease_cbk()
while checking for the quorum.

Patch already posted, and as this is a bug fix and not an enhancement to the leases feature, moving the reference to a bug.

Comment 1 Worker Ant 2018-10-31 00:32:38 UTC
REVIEW: https://review.gluster.org/21495 (afr/lease: Read child nodes from lease structure) posted (#3) for review on release-4.1 by Shyamsundar Ranganathan

Comment 2 Worker Ant 2018-10-31 14:19:33 UTC
REVIEW: https://review.gluster.org/21495 (afr/lease: Read child nodes from lease structure) posted (#3) for review on release-4.1 by Shyamsundar Ranganathan

Comment 3 Shyamsundar 2018-11-29 15:26:07 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.1.6, please open a new bug report.

glusterfs-4.1.6 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-November/000116.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.