Description of problem: Mandatory-locks feature has gone into release-3.8 branch. But locks.mandatory-locking volume set option is defined under op-version 4.0.0 which is wrong. { .key = "locks.mandatory-locking", .voltype = "features/locks", .op_versionGD_OP_VERSION_4_0_0, .validate_fn = validate_mandatory_locking, }, Version-Release number of selected component (if applicable): mainline
REVIEW: http://review.gluster.org/14180 (mgmt/glusterd: Fix op-version for mandatory-locking volume set option) posted (#1) for review on master by Anoop C S (anoopcs)
COMMIT: http://review.gluster.org/14180 committed in master by Atin Mukherjee (amukherj) ------ commit 717e66a799b70c9b61ad56ab9d27915e265f9d3d Author: Anoop C S <anoopcs> Date: Tue May 3 12:50:51 2016 +0530 mgmt/glusterd: Fix op-version for mandatory-locking volume set option The following volume set option will be available with 3.8 release. locks.mandatory-locking This one-line change is to fix the wrongly set op-version for the above mentioned volume set option. Change-Id: Icc7d213f917f5f69e2ec84c685b1138ce2f86a90 BUG: 1332413 Signed-off-by: Anoop C S <anoopcs> Reviewed-on: http://review.gluster.org/14180 NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> CentOS-regression: Gluster Build System <jenkins.com>