Description of problem: ======================= Currently the validation is upto 3 values but it does not validate further. Ideally anything which is not in exact format (Y-m-d H:M:S) should fail. [root@dhcp42-7 scripts]# gluster volume geo-replication master 10.70.43.249::slave config checkpoint 2017-03-05 15:30:45:10:11:12:13 geo-replication config updated successfully [root@dhcp42-7 scripts]# [root@dhcp42-7 scripts]# gluster volume geo-replication master 10.70.43.249::slave config checkpoint 2017-03-05 15:30:45:aa:bb:cc geo-replication config updated successfully [root@dhcp42-7 scripts]# Version-Release number of selected component (if applicable): ============================================================= glusterfs-geo-replication-3.8.4-17.el7rhgs.x86_64 How reproducible: ================= Always
Geo-replication support added to Glusterd2 project, which will be available with Gluster upstream 4.0 and 4.1 releases. Most of the issues already fixed with issue https://github.com/gluster/glusterd2/issues/271 and remaining fixes are noted in issue https://github.com/gluster/glusterd2/issues/557 We can close these issues since we are not planning any fixes for 3.x series.
Fix required in `$SRC/cli/src/cli-cmd-parser.c`(handle error after strptime)
https://bugzilla.redhat.com/show_bug.cgi?id=1651584
REVIEW: https://review.gluster.org/21692 (geo-rep: validate the config checkpoint date format)
*** Bug 1672979 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0658