this bug is to track the fix which was already in 3.1.2 but missed out as part of rebasing to 3.1.3 from upstream 3.7.9
downstream patch for this bug: https://code.engineering.redhat.com/gerrit/70324
Verified this bug using the build "glusterfs-3.7.9-1". Set a key/value longer than 4096 characters for a volume and restarted glusterd, restart worked properly without any error message. Steps done to verify: ===================== 1. Set the volume option "auth.allow" with 4109 characters 2. Restarted glusterd With these details, moving the bug to verified state
LGTM :)
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-2016:1240