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.

Description of problem:

Radiusd does not trigger modules.sql.fail trap if it can't connect to mysql server. It triggers only modules.sql.close, but there is written in trigger.conf, that fail and close are two different actions.

# A connection to the DB has been closed
close = "${snmptrap}::serverModuleConnectionDown ${args}"

# Failed to open a new connection to the DB
fail = "${snmptrap}::serverModuleConnectionFail ${args}"

It is a regression. Older version freeradius-3.0.4-7.el7_3 triggers it.

See radiusd log files for old and new version or run reproducer trigger_reproducer.sh.


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

freeradius-3.0.12-1.el7


How reproducible:

100%


Steps to Reproduce:

1, Install dependencies.

yum install -y freeradius freeradius-utils net-snmp net-snmp-utils freeradius-mysql mariadb-server mariadb-libs mariadb

Run trigger_reproducer.sh, it is attached, and check radiusd log, which is printed in the end of the reproducer.

trigger_reproducer.sh


Actual results:

Radiusd does not trigger modules.sql.fail if it can't connect to MySQL server.


Expected results:

Radius triggers modules.sql.fail.

Created attachment 1256525 [details]
Reproducer script.

Created attachment 1256526 [details]
Log file for the old version of freeradius.

Created attachment 1256527 [details]
Log file for the new version of freeradius.

Issue reported upstream: https://github.com/FreeRADIUS/freeradius-server/issues/1923

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://access.redhat.com/errata/RHEA-2017:1954