REVIEW: https://review.gluster.org/21692 (geo-rep: validate the config checkpoint date format) posted (#3) for review on master by Shwetha K Acharya
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): ============================================================= mainline How reproducible: ================= Always
REVIEW: https://review.gluster.org/21692 (geo-rep: validate the config checkpoint date format) posted (#6) for review on master by Kotresh HR
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-6.0, please open a new bug report. glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/