-
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
[DPB][FLEX Counters] Error seen in SDK reading counters for removed ports #19105
Comments
@dgsudharsan to start a offline discussion on the change needed in Sairedis. |
this PR sonic-net/sonic-swss#3076 has the fix for this issue. Please retest with latest master image. |
@arlakshm Thanks for your comment. |
@pavannaregundi From the internally attached PR I see the backref was missing and hence the queue removal didn't happen in the first place. The PR 3076 in SWSS addresses a different race condition which is a statistical issue. I believe we need the yang fix that is linked to this bug. |
I had directly patched changes to /usr/local/yang-models/sonic-buffer-queue.yang in sonic switch and tried that change. It did not work either. So internally we are still checking it. |
can you try configuring |
@stephenxs Thanks. We will try this and get back. |
@stephenxs Adding create_only_config_db_buffers.json is working. However I am not sure if this is how it is supposed to work. |
Hi |
Description
Errors are seen in SDK reading the Queue and Buffer counters for deleted ports after dynamic breakout CLI execution.
Steps to reproduce the issue:
Describe the results you received:
From the collected logs in redis-dump,
redis_flex_after_breakout.txt: Stale entries present in FLEX_DB for queues mapped to deleted port.
Describe the results you expected:
Output of
show version
:port_breakout_info.txt
redis_asic_after_breakout.txt
redis_asic_before_breakout.txt
redis_flex_after_breakout.txt
redis_flex_before_breakout.txt
syslog.txt
Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: