Bug 1305493

Summary: glusterfs logrotate config file clobbers defaults [rhel-6]
Product: Red Hat Enterprise Linux 6 Reporter: Marcel Kolaja <mkolaja>
Component: glusterfsAssignee: sankarshan <sankarshan>
Status: CLOSED ERRATA QA Contact: Anoop <annair>
Severity: high Docs Contact:
Priority: high    
Version: 6.6CC: cww, jkaluza, jkurik, kevin, mnavrati, mpoole, nlevinki, nparmar, olim, peak, phracek, rcyriac, rhs-bugs, rnichols42, rsawhill, salmy, sankarshan, sasundar, smohan, storage-qa-internal, tbowling, vbellur, zpytela
Target Milestone: rcKeywords: Patch, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.6.0.55-1 Doc Type: Bug Fix
Doc Text:
When installing the glusterfs packages on Red Hat Enterprise Linux 6, the glusterfs-logrotate and glusterfs-georep-logrotate files were previously installed with several global logrotate options. Consequently, the global options affected the default settings in the /etc/logrotate.conf file. The glusterfs RPMs have been rebuilt to prevent the default settings from being overridden. As a result, global settings in /etc/logrotate.conf continue to function as configured without being overridden by settings from glusterfs logrotate files.
Story Points: ---
Clone Of: 1171865 Environment:
Last Closed: 2016-03-22 15:43:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1171865    
Bug Blocks:    

Description Marcel Kolaja 2016-02-08 12:29:35 UTC
This bug has been copied from bug #1171865 and has been proposed
to be backported to 6.7 z-stream (EUS).

Comment 3 Marcel Kolaja 2016-02-10 10:32:12 UTC
*** Bug 1279968 has been marked as a duplicate of this bug. ***

Comment 8 Anoop 2016-03-15 15:52:37 UTC
Verified by QE.

Comment 11 errata-xmlrpc 2016-03-22 15:43:59 UTC
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-0476.html