Description of problem: The glusterfs-logrotate (and glusterfs-georep-logrotate) file from the RPM contains several global logrotate options, such as "weekly", "rotate 52" and "compress" which are clobbering the default logrotate settings from /etc/logrotate.conf Version-Release number of selected component (if applicable): 3.6.0.29-2.el6 How reproducible: 100% Actual results: logrotate is keeping 52 weeks of compressed logs for all files not explicitly overriding the defaults. Expected results: logrotate should be honoring weekly, rotate 4 and no compress as per /etc/logrotate.conf shipped by default.
Upon review, this was fixed upstream here: https://forge.gluster.org/glusterfs-core/glusterfs/commit/a5d73daabf6df95bc73b186d92f3e2d1239a6f8a
*** Bug 1181315 has been marked as a duplicate of this bug. ***
Added gss tracker bz's. because qemu-kvm depends on glusterfs-api, this results in any rhel 6.6/7.1 kvm hypervisor inheriting this logrotate config bug. The following bz's resulted - bz1195947 - Reduce the contents of dependencies from glusterfs-api - bz1194503 - Dependency problem due to glusterfs-api depending on glusterfs instead of only glusterfs-libs [rhel-6] - bz1194508 - Dependency problem due to glusterfs-api depending on glusterfs instead of only glusterfs-libs [rhel-7]
The short term fix for this is to correct the rsyslog configuration error. I believe that was being addressed on bz1099539 for RHS. Is this short term fix being addressed for RHEL 6.7? I thought it was on this BZ but do not see any updates reflecting that. It should be a very simple fix to release quickly.
*** Bug 1266210 has been marked as a duplicate of this bug. ***
Tested with glusterfs-3.7.5-19.el6rhs and here are the observations 1. When qemu-kvm is installed, it pulls in glusterfs-api, glusterfs, glusterfs-libs and glusterfs-client-xlators [root@ ~]# rpm -qR qemu-kvm | grep gluster glusterfs-api [root@ ~]# rpm -qR glusterfs-api | grep gluster glusterfs = 3.7.5-19.el6 glusterfs-client-xlators = 3.7.5-19.el6 libglusterfs.so.0()(64bit) [root@ ~]# rpm -qR glusterfs | grep gluster glusterfs-libs = 3.7.5-19.el6 libglusterfs.so.0()(64bit) [root@ ~]# rpm -qR glusterfs-libs | grep gluster libglusterfs.so.0()(64bit) [root@ ~]# rpm -qR glusterfs-client-xlators | grep gluster libglusterfs.so.0()(64bit) 2. No glusterfs binaries are installed as part of the above rpms and its dependencies installation [root@ ~]# which glusterfs /usr/bin/which: no glusterfs in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) [root@ ~]# which glusterfs /usr/bin/which: no glusterfs in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) [root@ ~]# which glusterfsd /usr/bin/which: no glusterfsd in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) [root@ ~]# which gluster /usr/bin/which: no gluster in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) [root@ ~]# ls /usr/sbin/glusterfs ls: cannot access /usr/sbin/glusterfs: No such file or directory [root@ ~]# ls /usr/sbin/glusterfs* ls: cannot access /usr/sbin/glusterfs*: No such file or directory [root@ ~]# ls /usr/sbin/gluster* ls: cannot access /usr/sbin/gluster*: No such file or directory 3. When installing glusterfs-fuse, it adds the logrotate conf file, which only logrotates glusterfs log files and glusterfs binaries. But glusterfs-fuse not made pulled in as a dependency by any other packages. 4. logrotate conf file has the content # Rotate client logs /var/log/glusterfs/*.log { sharedscripts weekly rotate 52 missingok compress delaycompress notifempty postrotate /usr/bin/killall -HUP glusterfs > /dev/null 2>&1 || true /usr/bin/killall -HUP glusterd > /dev/null 2>&1 || true endscript } # Rotate server logs /var/log/glusterfs/bricks/*.log { sharedscripts weekly rotate 52 missingok compress delaycompress notifempty postrotate /usr/bin/killall -HUP glusterfsd > /dev/null 2>&1 || true endscript } Based on the above observations, verifying this bug
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://rhn.redhat.com/errata/RHBA-2016-0747.html