Skip to content

syslog: accept standard rsyslogd rate-limit message in test_syslog_rate_limit#1247

Merged
bingwang-ms merged 1 commit into
Azure:202512from
bingwang-ms:fix/syslog-rate-limit-rsyslogd-msg-compat-202512
Jun 19, 2026
Merged

syslog: accept standard rsyslogd rate-limit message in test_syslog_rate_limit#1247
bingwang-ms merged 1 commit into
Azure:202512from
bingwang-ms:fix/syslog-rate-limit-rsyslogd-msg-compat-202512

Conversation

@bingwang-ms

Copy link
Copy Markdown
Contributor

Cherry-pick of sonic-net/sonic-mgmt#25494 to 202512 branch.

Description of PR

Summary:
Fix test_syslog_rate_limit failure on platforms where rsyslogd emits a different rate-limit message.

rsyslogd emits two different messages depending on version when rate-limiting triggers:

  • "begin to drop messages due to rate-limiting" — logged when drops start (transition 0→1)
  • "N messages lost due to rate-limiting (M allowed within K seconds)" — logged as a summary when the rate-limit window ends

Both are standard rsyslogd messages from ratelimit.c. The test only matched the first form, causing failures on rsyslogd versions that emit the summary form.

This fix uses regex alternation to accept either form. The 202512 branch additionally had an overly specific pattern with a rate-limit-test>: prefix that would not match the summary message form.

Type of change

  • Bug fix

…te_limit

The test expected only SONiC's patched rsyslogd message:
  'begin to drop messages due to rate-limiting'

Standard rsyslogd (used on some platforms) emits a different message:
  'N messages lost due to rate-limiting (M allowed within K seconds)'

Both messages indicate that rate limiting is working correctly. Use
regex alternation to accept either form, making the test work across
different rsyslogd builds.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Bing Wang <bingwang@microsoft.com>
@bingwang-ms bingwang-ms merged commit 2640357 into Azure:202512 Jun 19, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant