[Bugs] [Bug 1463512] New: USS: stale snap entries are seen when activation/ deactivation performed during one of the glusterd's unavailability

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1463512

            Bug ID: 1463512
           Summary: USS: stale snap entries are seen when
                    activation/deactivation performed during one of the
                    glusterd's unavailability
           Product: GlusterFS
           Version: 3.11
         Component: snapshot
          Keywords: Triaged
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: rkavunga at redhat.com
                CC: bugs at gluster.org
        Depends On: 1448150
            Blocks: 1165648



+++ This bug was initially created as a clone of Bug #1448150 +++

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:

--- Additional comment from Worker Ant on 2017-05-04 11:57:34 EDT ---

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 at redhat.com)

--- Additional comment from Worker Ant on 2017-05-05 03:07:59 EDT ---

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 at redhat.com)

--- Additional comment from Worker Ant on 2017-05-08 01:49:52 EDT ---

COMMIT: https://review.gluster.org/17178 committed in master by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit 21115ae8b80c1ae0afe8427423ca5ecde40f0027
Author: Mohammed Rafi KC <rkavunga at redhat.com>
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 at redhat.com>
    Reviewed-on: https://review.gluster.org/17178
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1165648
[Bug 1165648] [USS]: If glusterd goes down on the originator node while
snapshots are activated, after glusterd comes back up, accessing .snaps do
not list any snapshots even if they are present
https://bugzilla.redhat.com/show_bug.cgi?id=1448150
[Bug 1448150] USS: stale snap entries are seen when activation/deactivation
performed during one of the glusterd's unavailability
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.