Bug 1981457

Summary: Keepalived 2.1.5 breaks integration with rsyslog using --log-facility(-S) option
Product: Red Hat Enterprise Linux 8 Reporter: Nicolas Wildner <nwildner>
Component: keepalivedAssignee: Ryan O'Hara <rohara>
Status: CLOSED DUPLICATE QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.4CC: cluster-maint
Target Milestone: beta   
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: 2021-07-12 15:30:05 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:

Description Nicolas Wildner 2021-07-12 15:21:01 UTC 
Description of problem:

Upgrading keepalived to 2.1.5 on RHEL8 or doing a fresh install of this version breaks the --log-facility(-S) rsyslog integration feature 

Version-Release number of selected component (if applicable):

keepalived-2.1.5-6.el8.x86_64 

How reproducible:

Always. Downgrading keepalived to 2.0.10 solves the issue

Steps to Reproduce:
1. Create a custom syslog facility:

    # echo "local0.*  /var/log/keepalived.log" > /etc/rsyslog.d/keepalived.conf

2. Enable --log-facility(-S) with the same log facility level on keepalived:

    # sed -i 's|KEEPALIVED_OPTIONS="-D"|KEEPALIVED_OPTIONS="-D -d -S 0"|g' /etc/sysconfig/keepalived 

3. Restart keepalived and rsyslog:

    systemctl restart rsyslog
    systemctl restart keepalived


Actual results:

keepalived keeps writing to /var/log/messages


Expected results:

keepalived should write to any logfile configured on a rsyslog custom facility

Additional info:

There is a discussion on keepalived upstream that seems to be related with this regression here: https://github.com/acassen/keepalived/issues/1836

Some commits got reverted while others pushed to fix this issue.

Also, see case 02983056 for further information.
Comment 1 Ryan O'Hara 2021-07-12 15:30:05 UTC 

*** This bug has been marked as a duplicate of bug 1977716 ***