Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/17172 (fd: We should use dict_set_uint64 to store fd->pid) posted (#1) for review on master by Zhou Zhengping (johnzzpcrystal)
COMMIT: https://review.gluster.org/17172 committed in master by Jeff Darcy (jeff.us) ------ commit 9f930646eeed12a243d083c91acb59fbe7004074 Author: Zhou Zhengping <johnzzpcrystal> Date: Wed May 3 18:33:40 2017 +0800 fd: We should use dict_set_uint64 to store fd->pid Change-Id: I136372b9929d3ecf243649b6945571a67bfd80eb BUG: 1447828 Signed-off-by: Zhou Zhengping <johnzzpcrystal> Reviewed-on: https://review.gluster.org/17172 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts> Tested-by: Amar Tumballi <amarts> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
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.12.0, please open a new bug report. glusterfs-3.12.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/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/