Description of problem: ======================= Changelog-log-level is an config option to set the log level for changelog to one of the following: CRITICAL, ERROR, WARNING, INFO, DEBUG, TRACE So the cli should valid the input and fail if it is anything else. But it is allowed to set any junk value as follows: [root@dhcp42-7 vol0]# gluster volume geo-replication vol0 10.70.43.249::vol1 config changelog-log-level test geo-replication config updated successfully [root@dhcp42-7 vol0]# gluster volume geo-replication vol0 10.70.43.249::vol1 config changelog-log-level test [root@dhcp42-7 vol0]# gluster volume geo-replication vol0 10.70.43.249::vol1 config changelog-log-level zyzshajdhjsd geo-replication config updated successfully [root@dhcp42-7 vol0]# [root@dhcp42-7 vol0]# [root@dhcp42-7 vol0]# gluster volume geo-replication vol0 10.70.43.249::vol1 config changelog-log-level zyzshajdhjsd [root@dhcp42-7 vol0]# Version-Release number of selected component (if applicable): ============================================================= glusterfs-geo-replication-3.8.4-13.el7rhgs.x86_64 How reproducible: ================= Always Steps to Reproduce: =================== 1. Set some value using gluster volume geo-replication vol0 10.70.43.249::vol1 config changelog-log-level <value>
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 available upstream: https://review.gluster.org/#/c/glusterfs/+/18257/
Fix referenced is merged. Should this be moved to ON_QA for verification?
I think it is already verified. Kshithij, can you confirm so that we can close this bz.
Thanks Kshithij for your input. The patch mentioned in comment #6 fixed this bug.