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

Get bgp neighbor information only if bgp service is in critical process #7046

Closed
wants to merge 2 commits into from

Conversation

SuvarnaMeenakshi
Copy link
Contributor

Signed-off-by: Suvarna Meenakshi sumeenak@microsoft.com
(cherry picked from commit 39f1d5a8c41f678f876952da7f48492fa5873635)

Description of PR

Summary:
Fixes # (issue)

Type of change

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

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

Container autorestart test fails on supervisor with error:
RunAnsibleModuleFail: run module bgp_facts failed, Ansible Results => {"changed": false, "failed": true, "msg": "Command failed rc=1, out=, err=Error response from daemon: Container f494b23f9428414d38b7ad8604a712914cbfee9dda5e9294f442779b6a1c1101 is not running\n"}
autorestart/test_container_autorestart.py:419: in run_test_on_single_container
up_bgp_neighbors = duthost.get_bgp_neighbors_per_asic("established")
This is seen after sonic-net/sonic-buildimage#11796 where bgp service is disabled on supervisor.

How did you do it?

get bgp neighbor information only if bgp container name is in the duthost critical_service list.

How did you verify/test it?

Ran autorestart test on chassis platform and test passes.

Any platform specific information?

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

Documentation

and added in critical process list.

Signed-off-by: Suvarna Meenakshi <sumeenak@microsoft.com>
(cherry picked from commit 39f1d5a8c41f678f876952da7f48492fa5873635)
Signed-off-by: Suvarna Meenakshi <sumeenak@microsoft.com>
@SuvarnaMeenakshi
Copy link
Contributor Author

closing this as #7042 should fix the issue

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

Successfully merging this pull request may close these issues.

2 participants