+++ This bug was initially created as a clone of Bug #1388401 +++ +++ This bug was initially created as a clone of Bug #1380122 +++ Description of problem: When assigning a label to a checkpoint, geo-replication status will throw: No active geo-replication sessions between [masternode] and [geo-rep target] Steps to Reproduce: 1. Set up a geo-replication session 2. Once started, create a checkpoint like this: # gluster volume geo-replication rep01 RHGS3::slave config checkpoint chris 3. Run # gluster volume geo-replication rep01 RHGS3::slave status Actual results: No active geo-replication sessions between rep01 and RHGS3::slave Expected results: MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED ---------------------------------------------------------------------------------------------------------------------------------------------- RHGS1 rep01 /rhs/brick1/rep01 root RHGS3::slave RHGS3 Active Changelog Crawl 2016-09-28 13:13:45 RHGS2 rep01 /rhs/brick1/rep01 root RHGS3::slave RHGS4 Passive N/A N/A Additional info: It seems like the geo-replication continues even though status says there is no active connection :( [root@RHGS1 rep01]# gluster volume geo-replication rep01 RHGS3::slave status MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED ---------------------------------------------------------------------------------------------------------------------------------------------- RHGS1 rep01 /rhs/brick1/rep01 root RHGS3::slave RHGS3 Active Changelog Crawl 2016-09-28 13:13:45 RHGS2 rep01 /rhs/brick1/rep01 root RHGS3::slave RHGS4 Passive N/A N/A [root@RHGS1 rep01]# gluster volume geo-replication rep01 RHGS3::slave config checkpoint chris geo-replication config updated successfully [root@RHGS1 rep01]# gluster volume geo-replication rep01 RHGS3::slave status No active geo-replication sessions between rep01 and RHGS3::slave [root@RHGS1 rep01]# gluster volume geo-replication rep01 RHGS3::slave config checkpoint now geo-replication config updated successfully [root@RHGS1 rep01]# gluster volume geo-replication rep01 RHGS3::slave status MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED ---------------------------------------------------------------------------------------------------------------------------------------------- RHGS1 rep01 /rhs/brick1/rep01 root RHGS3::slave RHGS3 Active Changelog Crawl 2016-09-28 13:13:45 RHGS2 rep01 /rhs/brick1/rep01 root RHGS3::slave RHGS4 Passive N/A N/A --- Additional comment from Aravinda VK on 2016-09-29 02:20:52 EDT --- Set the Checkpoint for current time using, gluster volume geo-replication rep01 RHGS3::slave config checkpoint now As mentioned in the description we need to validate for other inputs.(other than now)
REVIEW: http://review.gluster.org/15856 (geo-rep/cli: Validate Checkpoint label) posted (#1) for review on release-3.7 by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/15856 committed in release-3.7 by Aravinda VK (avishwan) ------ commit 7b1ca6061f6e4187e1457e7f32de0e8f2adcc854 Author: Aravinda VK <avishwan> Date: Tue Oct 25 12:56:05 2016 +0530 geo-rep/cli: Validate Checkpoint label Checkpoint command accepts "now" or any other Time in "%Y-%m-%d %H:%M:%S" format as label. Validation added with this patch for the input label. Checkpoint set will fail for invalid label. > Reviewed-on: http://review.gluster.org/15721 > Smoke: Gluster Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > NetBSD-regression: NetBSD Build System <jenkins.org> > Reviewed-by: Saravanakumar Arumugam <sarumuga> > Reviewed-by: Kotresh HR <khiremat> BUG: 1395628 Change-Id: I23518c151ab4b294f64cae3b78baaacb3d8f7b82 Signed-off-by: Aravinda VK <avishwan> (cherry picked from commit 8a1993b32f476765f9f5c9294e7c3f2ae75198a0) Reviewed-on: http://review.gluster.org/15856 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Saravanakumar Arumugam <sarumuga>
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.