Bug 1305493 - glusterfs logrotate config file clobbers defaults [rhel-6]
Summary: glusterfs logrotate config file clobbers defaults [rhel-6]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: glusterfs
Version: 6.6
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: sankarshan
QA Contact: Anoop
URL:
Whiteboard:
: 1279968 (view as bug list)
Depends On: 1171865
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-08 12:29 UTC by Marcel Kolaja
Modified: 2019-11-14 07:25 UTC (History)
23 users (show)

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.
Clone Of: 1171865
Environment:
Last Closed: 2016-03-22 15:43:59 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1353853 0 None None None 2016-02-08 12:29:48 UTC
Red Hat Product Errata RHBA-2016:0476 0 normal SHIPPED_LIVE glusterfs bug fix update 2016-03-22 19:38:44 UTC

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
Note You need to log in before you can comment on or make changes to this bug.