Skip to content

[syslog.yml]: Remove "Connection: Local"#652

Closed
praveen-li wants to merge 1 commit intosonic-net:masterfrom
praveen-li:syslog_connection_local
Closed

[syslog.yml]: Remove "Connection: Local"#652
praveen-li wants to merge 1 commit intosonic-net:masterfrom
praveen-li:syslog_connection_local

Conversation

@praveen-li
Copy link
Copy Markdown
Member

@praveen-li praveen-li commented Jun 28, 2018

Description of PR

[syslog.yml]: The module "Check syslog messages for the test message"must not use Connection: local.

This playbook is executed from controller. So "connection: local" will parse
/var/log/syslog of controller server instead of DUT log file.

Signed-off-by: Praveen Chaudhary pchaudhary@linkedin.com

Fixes # (issue)

Type of change

  • [- ] Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Approach

How did you do it?
Remove Connection Local in syslog.yml
How did you verify/test it?
http://172.25.11.20:8080/job/Run_Test_Cases_Msft_Ansible/74/console
Any platform specific information?
No
Supported testbed topology if it's a new test case?

Documentation

must not use Connection: local.

This playbook is executed from controller. So "connection: local" will parse
/var/log/syslog of controller server instead of DUT log file.

Signed-off-by: Praveen Chaudhary <pchaudhary@linkedin.com>

# Check Messages
- name: Check syslog messages for the test message
connection: local
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The intended behavior here is to test the remote syslog behavior, therefore we actually want to check the local syslog in this step, to ensure the DUT sends its messages to the remote syslog server, which should be running on the local machine.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Joe

Thanks for review. In this case, kindly let me know. Do we need to manually start a remote syslog server on Controller or below steps in playbook are sufficient for this.

My guess is : below 2 modules does the job of starting remote syslog server.

  • name: Add Rsyslog destination for testing
    39 become: true
    40 lineinfile:
    41 line: ". @{{ local_srcip }}:{{ syslog_port }}"
    42 dest: /etc/rsyslog.conf
    43 state: present
    44
    45 - name: Restart Syslog Daemon
    46 become: true
    47 service: name=rsyslog state=restarted

-- I do not see syslogs coming to controller on my setup.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, those lines configure rsyslog running on the DUT to be aware of the syslog server it should send to for the test. However, lines 51-95 should start the remote syslog server on the Ansible host.

@praveen-li praveen-li closed this Jul 19, 2018
wangxin pushed a commit to wangxin/sonic-mgmt that referenced this pull request Oct 27, 2025
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
Submodule src/sonic-swss 24fcbb6..3cee6b8:
  > [aclorch]: Fix table name in counter table for mirror rules (sonic-net#1060)
  > Cannot ping to link-local ipv6 interface address of the switch. (sonic-net#774)
  > [MirrorOrch]: Mirror Session Retention across Warm Reboot (sonic-net#1062)

Submodule src/sonic-utilities afaedb7..a06bee7:
  > [201811][config] Add '-h' and '-?' as help options to unify with show/sonic-clear cmds (sonic-net#654)
  > Revert "Fixed config Asym PFC CLI. (sonic-net#632)" (sonic-net#652)

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
* [201811][swss][utilities] advance sub module head

Submodule src/sonic-swss fcd091c..9585be4:
  > [teamsyncd]: Check if LAG exists before removing (sonic-net#1069)
  > [mirrororch]: Toggle the mirror session when moving between VLAN/non-VLAN (sonic-net#1078)

Submodule src/sonic-utilities 7bb6ffb..2d721de:
  > [show] Properly replace port name with alias in command output (sonic-net#664)
  > [neighbor_advertiser] hand pick partial change from sonic-net#525 (sonic-net#689)
  > Revert "Revert "Fixed config Asym PFC CLI. (sonic-net#632)" (sonic-net#652)"

Signed-off-by: Ying Xie <ying.xie@microsoft.com>

* address compile issue

Submodule src/sonic-swss 9585be4..2529d79:
  > [mirrororch]: Address compiler switch issue (sonic-net#1079)

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
Pterosaur pushed a commit to Pterosaur/sonic-mgmt that referenced this pull request Mar 26, 2026
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.

2 participants