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/17198 (rpc: use GF_ATOMIC_INC to generate rpc_clnt's callid) posted (#1) for review on master by Zhou Zhengping (johnzzpcrystal)
COMMIT: https://review.gluster.org/17198 committed in master by Raghavendra G (rgowdapp) ------ commit e0aaaccefdfda345b981b86dea23b2ffa52e9377 Author: Zhou Zhengping <johnzzpcrystal> Date: Sun May 7 17:29:26 2017 +0800 rpc: use GF_ATOMIC_INC to generate rpc_clnt's callid Change-Id: I57ad970411db1ccd3d2c56c504c7da9cc221051f BUG: 1448692 Signed-off-by: Zhou Zhengping <johnzzpcrystal> Reviewed-on: https://review.gluster.org/17198 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp>
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/