Skip to content

Revert "Fix the issue introduced by the PR #16716"#17616

Merged
StormLiangMS merged 1 commit intomasterfrom
revert-17516-fix_pr_issue
Mar 20, 2025
Merged

Revert "Fix the issue introduced by the PR #16716"#17616
StormLiangMS merged 1 commit intomasterfrom
revert-17516-fix_pr_issue

Conversation

@wangxin
Copy link
Collaborator

@wangxin wangxin commented Mar 20, 2025

Reverts #17516

Originally #17516 was intended to fix an issue introduced in #16716. However, it turns out that it does not work.
We have to revert #16716. Before reverting 16716, #17516 must be reverted first. Otherwise, there will be conflicts.

@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@StormLiangMS StormLiangMS merged commit 727dcdf into master Mar 20, 2025
9 of 18 checks passed
BYGX-wcr added a commit to BYGX-wcr/sonic-mgmt that referenced this pull request Mar 21, 2025
amulyan7 pushed a commit to amulyan7/sonic-mgmt that referenced this pull request Mar 31, 2025
OriTrabelsi pushed a commit to OriTrabelsi/sonic-mgmt that referenced this pull request Apr 1, 2025
@wangxin wangxin deleted the revert-17516-fix_pr_issue branch July 4, 2025 03:23
opcoder0 pushed a commit to opcoder0/sonic-mgmt that referenced this pull request Dec 8, 2025
gshemesh2 pushed a commit to gshemesh2/sonic-mgmt that referenced this pull request Dec 21, 2025
gshemesh2 pushed a commit to gshemesh2/sonic-mgmt that referenced this pull request Jan 26, 2026
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
…g server's source address is configured (sonic-net#17616) (sonic-net#18514)

### Why I did it

An in-band syslog server will not receive any syslog if it is configured without a VRF specified, which is because `eth0` is always specified as the `device` of a syslog server and the syslog packets will be sent to `eth0` regardless of its destination IP address.

### How I did it

Pass the option "device" in rsyslog.conf only if when syslog server's source address is configured with a non-default VRF

#### How to verify it

Manually test:
1. Configuring a syslog server without VRF specified or with `default` as the VRF: no `device` passed in `rsyslog.conf`
2. Configuring a syslog server with non-default VRF: the configured VRF passed as `device` in `rsyslog.conf`

Co-authored-by: Stephen Sun <[email protected]>
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.

3 participants