Bug 1225441

Summary: corosync does not rotate its logs in /var/log/cluster
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Jelinek <tojeline>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: ccaulfie, cluster-maint, jkortus, sbradley
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: corosync-2.3.4-6.el7 Doc Type: Bug Fix
Doc Text:
This BZ doesn't need doc text.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 11:41:32 UTC Type: Bug
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:    
Bug Blocks: 1163671    
Attachments:
Description Flags
Proposed patch none

Description Tomas Jelinek 2015-05-27 11:33:44 UTC 
In bz1163671 it has been requested that pcs should setup corosync in such a way that corosync logs to /var/lib/cluster/corosync.log file. However corosync does not rotate rotate logs in this location which is a prerequisite.
Comment 1 Jan Friesse 2015-06-19 15:45:51 UTC 
Created attachment 1040993 [details]
Proposed patch
Comment 4 Jan Friesse 2015-07-03 13:45:37 UTC 
Unit test:
Corosync package includes /etc/logrotate.d/corosync file which log rotates  /var/log/cluster/corosync.log.
Comment 5 Jaroslav Kortus 2015-09-10 09:27:22 UTC 
Verified that the logrotate snippet is delivered as part of corosync-2.3.4-7.el7.x86_64 and that it really rotates the log file.

# rpm -ql corosync | grep logrot
/etc/logrotate.d/corosync

crm_report is processing the rotated files.
Comment 6 errata-xmlrpc 2015-11-19 11:41:32 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-2015-2354.html