Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LLDP: Add multi-asic support for test_lldp_entry_table_after_syncd_orchagent and some other fixes. #16640

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

wumiaont
Copy link
Contributor

…chagent and some other fixes.

Description of PR

test_lldp_entry_table_after_syncd_orchagent is a new test case added to test_lldp_syncd recently. It does not provide multi-asic support at this moment.

This PR add following supports to test_lldp_entry_table_after_syncd_orchagent :

  1. Added multi-asic support.

  2. Replace "docker restart" to "sudo systemctl restart". In OC pre-tests feature autorestart is always disabled. Container restart could cause corresponding service to go down. If autorestart is not enabled service will not try to come back up.

  3. Get the lldp key entry before restart swss. Current code is getting LLDP key after restart swss and all critical services are up. There's window of that some ports are not completely up or ports are up but or LLDP packets have not been received and processed yet. This could result get_lldp_entry_keys does not have the full set of keys and result following ports up check pass quickly. Result in following LLDP check to fail.

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?

Fix test_lldp_entry_table_after_syncd_orchagent failure

How did you do it?

How did you verify/test it?

Test passed consistently after code change.

Any platform specific information?

master

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

@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

2 participants