Loading config before getting red_min_threshold value.#989
Open
iris00522 wants to merge 3 commits intosonic-net:masterfrom
Open
Loading config before getting red_min_threshold value.#989iris00522 wants to merge 3 commits intosonic-net:masterfrom
iris00522 wants to merge 3 commits intosonic-net:masterfrom
Conversation
vincent201881
suggested changes
Jul 22, 2019
vincent201881
left a comment
There was a problem hiding this comment.
Maybe you could pre-check the "AZURE_LOSSY rmin " is already configured or not, if not exist then to config the AZURE_LOSSY.
Contributor
Author
|
@vincent201881 Please review again. |
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
5331ecd [vslib]: Fix MACsec bug in SCI and XPN (sonic-net#1003) ac04509 Fix build issues on gcc-10 (sonic-net#999) 1b8ce97 [pipeline] Download swss common artifact in a separated directory (sonic-net#995) 7a2e096 Change sonic-buildimage.vs artifact source from CI build to official build. (sonic-net#992) d5866a3 [vslib]: fix create MACsec SA error (sonic-net#986) f36f7ce Added Support for enum query capability of Nexthop Group Type. (sonic-net#989) 323b89b Support for MACsec statistics (sonic-net#892) 26a8a12 Prevent other notification event storms to keep enqueue unchecked and drained all memory that leads to crashing the switch router (sonic-net#968) 0cb253a Fix object availability conversion (sonic-net#974)
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
As part of this commit and previous commit ff6cb6c sonic-utilities submodule for 201911 has been updated to take following changes: Add support for QSFP-DD cables on 'show' command (sonic-net#989) [show] Fix for 'trunk' PortChannel reported as 'routed' port (sonic-net#1002) Enable HW watchdog before fast-reboot (sonic-net#977) [filter-fdb] Check VLAN Presence When Filter FDB (sonic-net#957) (sonic-net#975) [filter-fdb] Fix For Vlan Defined With No CIDR (sonic-net#976) [show/config]: combine feature and container feature cli (sonic-net#1015)
Pterosaur
pushed a commit
to Pterosaur/sonic-mgmt
that referenced
this pull request
Mar 25, 2026
### Description of PR
Summary:
Skipping swss event verification in telemetry/test_events.py for m1 and
m2 topos as this testing is out of scope for the deployment.
Fixes # (issue)
### Type of change
- [ ] Bug fix
- [ ] Testbed and Framework(new/improvement)
- [ ] New Test case
- [x] Skipped for non-supported platforms
- [ ] Test case improvement
### Approach
#### What is the motivation for this PR?
We were seeing failures while trying to verify the pfc storm event on m1
topos. This is because there is no QoS config. After inquiring with
Microsoft we decided to skip this part of the test since QoS is not
needed for the deployment.
#### How did you do it?
Refactored existing skip logic to use a list of hwsku's for skipping
instead of topology.
#### How did you verify/test it?
Verified the expected hwsku's were being skipped for broadcom.
#### Any platform specific information?
#### Supported testbed topology if it's a new test case?
### Documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
I get the two fail messages when we run the test item of ecn_wred .
1.TASK [test : Get WRED objects] *************************************************
fatal: [as7816-64x]: FAILED! => {"changed": true, "cmd": "docker exec database redis-cli -n 1 --eval /tmp/get_red_min.lua , 516096 | grep 516096", "delta": "0:00:00.190708", "end": "2019-07-04 03:43:29.729493", "failed": true, "failed_when_result": true, "invocation": {"module_args": {"_raw_params": "docker exec database redis-cli -n 1 --eval /tmp/get_red_min.lua , 516096 | grep 516096", "_uses_shell": true, "chdir": null, "creates": null, "executable": null, "removes": null, "warn": true}, "module_name": "command"}, "rc": 1, "start": "2019-07-04 03:43:29.538785", "stderr": "", "stdout": "", "stdout_lines": [], "warnings": []}
2.TASK [test : Restore original value] *******************************************
fatal: [as7816-64x]: FAILED! => {"changed": true, "cmd": "ecnconfig -p AZURE_LOSSY -rmin ", "delta": "0:00:00.090793", "end": "2019-07-04 03:43:30.075148", "failed": true, "failed_when_result": true, "invocation": {"module_args": {"_raw_params": "ecnconfig -p AZURE_LOSSY -rmin ", "_uses_shell": true, "chdir": null, "creates": null, "executable": null, "removes": null, "warn": true}, "module_name": "command"}, "rc": 2, "start": "2019-07-04 03:43:29.984355", "stderr": "usage: ecnconfig [-h] [-v] [-l] [-p PROFILE] [-gmin GREEN_MIN]\n [-gmax GREEN_MAX] [-ymin YELLOW_MIN] [-ymax YELLOW_MAX]\n [-rmin RED_MIN] [-rmax RED_MAX] [-gdrop GREEN_DROP_PROB]\n [-ydrop YELLOW_DROP_PROB] [-rdrop RED_DROP_PROB] [-vv]\n [-q QUEUE]\n [{on,off}]\necnconfig: error: argument -rmin/--red-min: expected one argument", "stdout": "", "stdout_lines": [], "warnings": []}
I think the issue is caused by getting red_min_threshold value fail.
TASK [test : set_fact] *********************************************************
ok: [as7816-64x] => {"ansible_facts": {"red_min_threshold": ""}, "changed": false, "invocation": {"module_args": {"red_min_threshold": ""}, "module_name": "set_fact"}}
Type of change
Approach
How did you do it?
I load the configuration file before running the test with getting red_min_threshold value.
Add the test steps, the two issues can be fixed.
How did you verify/test it?
Tested on the broadcom platform.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation