-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Multiple LAG flaps are noticed after warm reboot #6773
Comments
Just tested the latest of 202012 and the issue is not seen there. I think this has always been only master branch issue, and I was mistaken to tag 202012 here. |
This is now a priority issue as some of the other SAI issues seem to have been solved. The first warmboot goes through and no lag-flaps are noticed. However, after/during second warm-reboot, LAG flaps are pretty consistently noticed. I will post an update shortly. |
The LAGs flap due to swss restart as a SELECT TIMEOUT failure is seen in INIT_VIEW processing It looks like Orchagent is not reconciled and syncd did not respond within 60s. This led to to
|
From the logs, it also appears that vxlanmgrd is stuck for orchagent to reconcile. I tested using the fix provided in sonic-net/sonic-swss#1647 and the INIT_VIEW operation succeeded and the warm-reboot proceeded to APPLY_VIEW. |
This issue is not seen in the latest image in the manner it was seen before. However, LAGs still flap after warm-reboot. But, that is due to swss restart after warm-reboot due to SAI issue in syncd preshutdown. The new issue is tracked separately at |
Description
Warmboot proceeds as expected, and LAG interfaces and members are also added as expected.
After
WARMBOOT_FINALIZER
finishes, there is a system reload! (need to confirm and RCA this)Steps to reproduce the issue:
Describe the results you received:
Test failure log:
Syslog:
Describe the results you expected:
LAGs should not flap after warm reboot.
Output of
show version
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: