Description of problem: stale snap entries are seen in uss path when activation/deactivation performed during one of the glusterd's unavailability. Even if glusterd brought back to normal state, those stale entries are not synced. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.create a snapshot and activate it 2.enable uss 3.kill one glusterd 4. deactivate snapshot from other glusterd 5. bring back the dead glusterd. 6. check the snapshot entry in the uss path (this mount should be through the dead glusterd) Actual results: snapshot entry is listed Expected results: snapshot entry should not list, becaus it is deactivated Additional info:
REVIEW: https://review.gluster.org/17178 (snapview-server : Refresh the snapshot list during each reconnect) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: https://review.gluster.org/17178 (snapview-server : Refresh the snapshot list during each reconnect) posted (#2) for review on master by mohammed rafi kc (rkavunga)
COMMIT: https://review.gluster.org/17178 committed in master by Raghavendra Bhat (raghavendra) ------ commit 21115ae8b80c1ae0afe8427423ca5ecde40f0027 Author: Mohammed Rafi KC <rkavunga> Date: Thu May 4 20:56:43 2017 +0530 snapview-server : Refresh the snapshot list during each reconnect Currently we are refreshing the snapshot list either when there is a request from glusterd or the very first initialization. But if anything changed after when glusterd is down then there is no mechanism to refresh the snashot dentries. This patch will refresh snapshot list during each reconnect Change-Id: I3ed655572d777f60d57dd479d190f75553591267 BUG: 1448150 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: https://review.gluster.org/17178 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Raghavendra Bhat <raghavendra>
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/