Add neighsyncd check.#148
Draft
dypet wants to merge 1 commit into
Draft
Conversation
|
/azp run |
Signed-off-by: dypet <dypeters@cisco.com>
dypet
force-pushed
the
add_check_for_neighsyncd
branch
from
b685a38 to
76c6204
Compare
|
/azp run |
yue-fred-gao
approved these changes
Mar 13, 2026
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
3 participants
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.
What I did
Add a check for neighsyncd in swss.
Why I did it
neighsyncd in swss needs to be up and running before neigh resolve entries are programmed by hamgrd.
How I verified it
After adding sonic-net/sonic-buildimage#26174, brought up the containers and checked that neighbor entries are programmed after boot and config reload.
Details if related