Bug 1305492
| Summary: | glusterfs logrotate config file clobbers defaults [rhel-6] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | glusterfs | Assignee: | Milind Changire <mchangir> |
| Status: | CLOSED ERRATA | QA Contact: | Anoop <annair> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.6 | CC: | bsrirama, cww, jkaluza, kevin, mkolaja, mnavrati, mpoole, nlevinki, nparmar, olim, peak, phracek, rcyriac, rhs-bugs, rnichols42, rsawhill, salmy, sankarshan, sasundar, smohan, storage-qa-internal, tbowling, vbellur, zpytela |
| Target Milestone: | rc | Keywords: | Patch, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.6.0.55-1.el6_6 | 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-04-28 14:50:10 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:28:12 UTC
Brew build for RHEL 6.6-Z is available at https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=10915559 Now moving BZ to ON_QA. Log rotate changes are verified. 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-0700.html |