Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionNicolas 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.
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.