Removing this from 3.1.3. Will be fixing it later.
Cloning this to master, and adding setting of the boolean in the init of snap scheduler, so that this bug can be removed from known issues
Patch sent to master : http://review.gluster.org/15857
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101319/
[root@dhcp43-49 ~]# getsebool -a |grep cron_system_cronjob_use_shares cron_system_cronjob_use_shares --> off [root@dhcp43-49 ~]# gluster v set all cluster.enable-shared-storage enable volume set: success [root@dhcp43-49 ~]# getsebool -a |grep cron_system_cronjob_use_shares cron_system_cronjob_use_shares --> off [root@dhcp43-49 ~]# snap_scheduler.py init snap_scheduler: Successfully initialised snapshot scheduler for this node [root@dhcp43-49 ~]# getsebool -a |grep cron_system_cronjob_use_shares cron_system_cronjob_use_shares --> on [root@dhcp43-49 ~]gluster snapshot list Scheduled-job1-vol0_GMT-2017.05.02-11.55.02 Scheduled-job1-vol0_GMT-2017.05.02-11.57.01 Scheduled-job1-vol0_GMT-2017.05.02-11.58.01 bug verified on build glusterfs-3.8.4-24.el7rhgs.x86_64
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-2017:2774
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days