+++ This bug was initially created as a clone of Bug #1238072 +++
The auth.ssl-allow option isn't being handled by the protol/server xlator. This is causing even simple addition and deletions from the ssl-allow option to require a restart of the volume to be applied.
REVIEW: http://review.gluster.org/11492 (protocol/server: Correctly reconfigure auth.ssl-allow) posted (#1) for review on release-3.7 by Kaushal M (email@example.com)
REVIEW: http://review.gluster.org/11492 (protocol/server: Correctly reconfigure auth.ssl-allow) posted (#2) for review on release-3.7 by Kaushal M (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/11492 committed in release-3.7 by Raghavendra G (email@example.com)
Author: Kaushal M <firstname.lastname@example.org>
Date: Wed Jul 1 11:44:53 2015 +0530
protocol/server: Correctly reconfigure auth.ssl-allow
Backport of https://review.gluster.org/11487
auth.ssl-allow wasn't being handled during reconfigure. This prevented
the ssl-allow list from being live reloaded.
Signed-off-by: Kaushal M <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Raghavendra G <firstname.lastname@example.org>
Tested-by: Raghavendra G <email@example.com>
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-3.7.3, please open a new bug report.
glusterfs-3.7.3 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.