Is it platform specific

generic

Importance or Severity

Critical

Description of the bug

In the test tests/dualtor_io/test_tor_failure.py, one dut could be rebooted by toggling the PDU.
While the switch is powered off, there could be broken log lines in syslog, causing the loganalyzer to fail:

The loganalyzer was initially disabled in the test but got enabled in PR: #17722

We need either disabled the loganalyzer again or handle this exception properly.

To find the loganalyzer failure, we can check this log in the pytest log:
25/12/2025 19:41:57 parallel.parallel_run L0167 DEBUG | Started process 1584327 running target "analyze_logs--"
25/12/2025 19:41:57 parallel.parallel_run L0167 DEBUG | Started process 1584371 running target "analyze_logs--"
25/12/2025 19:42:02 parallel.on_terminate L0099 INFO | process analyze_logs-- terminated with exit code 252
25/12/2025 19:42:02 parallel.on_terminate L0099 INFO | process analyze_logs-- terminated with exit code 0

(There is a bug in the exit code, it can be fixed by #21797)

Steps to Reproduce

Run the test case tests/dualtor_io/test_tor_failure.py::test_active_tor_reboot_upstream on a dualtor-AA testbed.
Check the loganalyzer log with PR #21797 in the test code.

Actual Behavior and Expected Behavior

I suggest disable the loganlyzer because there if power cycle reboot in the test.

Relevant log output

Output of show version

Attach files (if any)

No response