-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Race condition between teamd and swss service. #2186
Labels
Comments
fixed with #2223 |
6 tasks
lguohan
pushed a commit
that referenced
this issue
May 27, 2022
Update submodule ptr for sonic-utilities to include [202111] [portchannel] Added ACL/PBH binding checks to the port before getting added to portchannel (#2186) Signed-off-by: Vivek Reddy Karri <[email protected]>
vivekrnv
pushed a commit
to vivekrnv/sonic-buildimage
that referenced
this issue
Aug 26, 2022
…c-net#2186) **What I did** To add a possibility to compile SONiC applications with address sanitizer (ASAN). > ASAN is a memory error detector for C/C++. It finds: > - Use after free (dangling pointer dereference) > - Heap buffer overflow > - Stack buffer overflow > - Global buffer overflow > - Use after return > - Use after the scope > - Initialization order bugs > - Memory leaks Add SIGTERM handling as a trigger to run a memory leak checker. **Why I did it** To add a possibility to detect memory errors in applications. **How I verified it** Compile SWSS with **--enable-asan** option. Install applications to DUT. Run tests that trigger different kinds of memory usage inside of applications. Stop applications with **SIGTERM** signal to trigger ASAN report generation. Reports will be placed in **/var/log/asan/** directory.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
With the new config mechanism (teammgrd) for teamd, the problem has become more noticeable.
The LAG state in stateDB created by teamsyncd has greater chance of being flushed by swss service.
It is time to add dependency on swss for teamd systemd service.
Steps to reproduce the issue:
1.
config lag/lag member
2.
restart system
3.
check stateDB
Describe the results you received:
The text was updated successfully, but these errors were encountered: