Bug 1402523 - Avoid corosync using copytruncate option in logrotate configuration when there's a support for better scheme in libqb
Summary: Avoid corosync using copytruncate option in logrotate configuration when ther...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1402521
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 18:05 UTC by Jan Pokorný [poki]
Modified: 2019-02-18 12:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-18 12:24:16 UTC
Target Upstream Version:

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

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