Bug 1402523

Summary: Avoid corosync using copytruncate option in logrotate configuration when there's a support for better scheme in libqb
Product: Red Hat Enterprise Linux 7 Reporter: Jan Pokorný [poki] <jpokorny>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED NEXTRELEASE QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: ccaulfie, cluster-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-18 12:24:16 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:
Bug Depends On: 1402521    
Bug Blocks:    

Description Jan Pokorný [poki] 2016-12-07 18:05:39 UTC
For a discussion, see original libqb bug [1402521] that the resolution
of this bug (most likely) depends on.

Comment 1 Jan Pokorný [poki] 2016-12-07 18:06:28 UTC
(the link was meant to be clickable: [bug 1402521])

Comment 3 Jan Friesse 2019-02-18 12:24:16 UTC
Corosync part is fixed in Corosync 3.x by https://github.com/corosync/corosync/pull/390.

RHEL 7 is currently in quite a late phase and adding this feature requires non-trivial changes in LibQB code (corosync part depends on LibQB change).

From upstream perspective - doesn't make too much sense to backport patch. copytruncate is far from perfect, but usually works quite well. And as mentioned, better solution is in (now stable) 3.x branch.

Closing this as a NextRelease.