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

[Bug]: test_lldp_neighbor_post_orchagent_reboot fails for multi-asic #14689

Open
anamehra opened this issue Sep 22, 2024 · 1 comment
Open

[Bug]: test_lldp_neighbor_post_orchagent_reboot fails for multi-asic #14689

anamehra opened this issue Sep 22, 2024 · 1 comment

Comments

@anamehra
Copy link
Contributor

Issue Description

#14616 introduced new test test_lldp_neighbor_post_orchagent_reboot
The test case does not handle multi-asic scenario and fails for multi-asic DUT

Results you see

On multi-asic platform, the tests try to disable swss0 feature. feature names should not be appended with namespace number.

      raise RunAnsibleModuleFail("run module {} failed".format(self.module_name), res)

E tests.common.errors.RunAnsibleModuleFail: run module shell failed, Ansible Results =>
E {"changed": true, "cmd": "sudo config feature autorestart swss0 disabled", "delta": "0:00:01.131598", "end": "2024-09-22 09:24:54.296006", "failed": true, "msg": "non-zero return code", "rc": 1, "start": "2024-09-22 09:24:53.164408", "stderr": "", "stderr_lines": [], "stdout": "Feature 'swss0' doesn't exist", "stdout_lines": ["Feature 'swss0' doesn't exist"]}

Results you expected to see

The test should pass on multi-asic as well

Is it platform specific

generic

Relevant log output

No response

Output of show version

No response

Attach files (if any)

No response

@anamehra
Copy link
Contributor Author

Hi @abdosi , for you viz.

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

No branches or pull requests

1 participant