Ignore mgmt_ds_lock error in loganalyzer due to expected behavior #21856
Conversation
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
Ignore expected FRR backend datastore lock contention during initialization - backends retry indefinitely until successful Signed-off-by: markxiao <markxiao@arista.com>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…rror-in-loganalyzer
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
StormLiangMS
approved these changes
Jan 8, 2026
Collaborator
StormLiangMS
left a comment
StormLiangMS
left a comment
There was a problem hiding this comment.
If this is by design, should FRR downgrade the log level to "notice" instead of "error"?
As we're moving from separate mode to unified mode for config initialization, I expect the race condition between staticd and zebra will be resolved once the transition is complete.
For now, I think it is ok to ignore this error logs.
@lipxu could you help to take a look?
StormLiangMS
added
the
Request for 202511 branch
vmittal-msft
added
Approved for 202511 branch
and removed
Approved for 202511 branch
labels
Collaborator
|
@markx-arista PR conflicts with 202511 branch |
PriyanshTratiya
pushed a commit
to PriyanshTratiya/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
…nic-net#21856) Ignore expected FRR backend datastore lock contention during initialization - backends retry indefinitely until successful Signed-off-by: markxiao <markxiao@arista.com> Signed-off-by: Priyansh Tratiya <ptratiya@microsoft.com>
AndoniSanguesa
pushed a commit
to AndoniSanguesa/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
…nic-net#21856) Ignore expected FRR backend datastore lock contention during initialization - backends retry indefinitely until successful Signed-off-by: markxiao <markxiao@arista.com> Signed-off-by: Andoni Sanguesa <andoniesanguesa@gmail.com>
AndoniSanguesa
pushed a commit
to AndoniSanguesa/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
…nic-net#21856) Ignore expected FRR backend datastore lock contention during initialization - backends retry indefinitely until successful Signed-off-by: markxiao <markxiao@arista.com> Signed-off-by: Andoni Sanguesa <andoniesanguesa@gmail.com>
saravanan-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Jan 22, 2026
…nic-net#21856) Ignore expected FRR backend datastore lock contention during initialization - backends retry indefinitely until successful Signed-off-by: markxiao <markxiao@arista.com> Signed-off-by: Saravanan Sellappa <saravanan@nexthop.ai>
Collaborator
|
@markx-arista could you help to resolve 202511 conflict issue? |
6 tasks
Contributor
Author
Cherry-pick to 202511: #22099 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Description of PR
Summary:
Ignore expected FRR backend datastore lock contention during initialization - backends retry indefinitely until successful
Backend daemons like zebra and staticd both try to acquire the lock during initialization, and zebra starts first, then staticd retries every 50ms until zebra finishes initialization and release the lock.
Zebra takes time to initialize on some SKUs, and causes the staticd to retry. However, lock contention and retry mechanism is by design. This log is expected and it only triggers loganalyzer error because its log level is ERR.
sonic-buildimage issue: sonic-net/sonic-buildimage#24966
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
test_bgp_router_id.py failed due to loganalyzer during bgp service restart
How did you do it?
Ignore the expected log
How did you verify/test it?
test_bgp_router_id.py passed
Any platform specific information?
We only saw the problem on Arista 7050CX3-32c because zebra takes a little bit longer time to initialize on it. Could happen to other SKUs.
Supported testbed topology if it's a new test case?
Documentation