Skip to content

LLDP: Fix issue with restart_orchagent as VOQ does not support warm restarting of orchagent (#16765)#218

Merged
arlakshm merged 1 commit intoAzure:202503from
wumiaont:202503
May 8, 2025
Merged

LLDP: Fix issue with restart_orchagent as VOQ does not support warm restarting of orchagent (#16765)#218
arlakshm merged 1 commit intoAzure:202503from
wumiaont:202503

Conversation

@wumiaont
Copy link

Description of PR
test_lldp_neighbor_post_orchagent_reboot uses prefix restart_orchagent() to warm restart orchagent. This warm restart of orchagent(kill orchagent and restart orchagent process) is not supported on chassis with type VOQ.

Add code to handle chassis type VOQ case by restarting the swss@0(1) service. This will cause ports to be removed from lldp table and add back in so we can test the issue found in #6560.

Summary:
Fixes # (issue)

Type of change
Bug fix
Testbed and Framework(new/improvement)
New Test case
Skipped for non-supported platforms
Test case improvement
Back port request
202012
202205
202305
202311
202405
202411
Approach
What is the motivation for this PR?
Currently test_lldp_neighbor_post_orchagent_reboot is failing against chassis with type VOQ. It's found warm restart of orchagent is not supported on VOQ type chassis.

How did you do it?
For VOQ type chassis, uses "systemctl restart swss@0(1)" instead.

How did you verify/test it?
After the fix the test passed consistently against VOQ type chassis.

Description of PR

Summary:
Fixes # (issue)

Type of change

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

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405

Approach

What is the motivation for this PR?

How did you do it?

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

Loading
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