Cast workaround for N/A counter values from 202412#1962
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Mirroring my reply from direct cast PR to 202605 (#1955 (comment)): @StormLiangMS , regarding your concerns:
I agree that there is a risk where failures are masked away - this is precisely why this was a temporary workaround limited to specific branches. This is a compromise that has been acknowledged when this temporary workaround is done for the 202412 and 202505 branch. Counter values also cannot go negative as unsigned ints are used for its storage, and anything not a number will cause issues in testing (i.e.
The existing FlexCounter implementation is unable to distinguish between ports - there is no notion of multiple ports where all ports are treated as the same. This is precisely why the full fix is needed fast. Any sort of check on interfaces will involve so many parts that it will either be extremely inperformant or become the full fix itself.
Will do. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1153496: ✅Stage BuildTrixie:
✅Stage Test:
|
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1153496: ✅Stage BuildTrixie:
|
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1153496: ✅Stage Test:
|
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1153496: ✅Stage Test:
|
|
vs tests CI are failing with redis issues in infra @StormLiangMS @lolyu : |
|
Tracked the recurring VS/DVS CI failure as a sonic-swss infrastructure/test flake: Failure signature from Azure build 1153496: DVS service readiness timeout with most services STOPPED ( |
|
Follow-up on the recurring VS/DVS CI flake: I opened a candidate sonic-swss test-infra fix: Recent history suggests the VS test job is flaky, not consistently broken. |
|
/azp run |
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1154487: ✅Stage Build:
✅Stage BuildAsan:
|
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1154487: ✅Stage Build:
✅Stage BuildAsan:
|
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1154487: ✅Stage Build:
✅Stage BuildAsan:
|
Casting temp-workaround for N/A counters on management ports on 202605. This impacts all hwsku-topo combos that uses management ports (including TH5). Casting from: Azure/sonic-sairedis.msft#69 Proper fix under review at: master: sonic-net#1774 202511: sonic-net#1862 202605: Opened soon Signed-off-by: Justin Wong <jvwong@arista.com>
Signed-off-by: Justin Wong <jvwong@arista.com>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Cherry-pick PR to 202605: #1967 |
|
Cherry-pick PR to 202605: #1970 |
Description of PR
Summary:
Casting workaround for N/A counters on management ports on Broadcom platforms. This impacts all hwsku-topo combos that uses management ports (including TH5).
Casting from:
Azure/sonic-sairedis.msft#69
Proper fix under review at:
master: #1774
202511: #1862
202605: #1956
Fixes #1753 (temporary fix)
Type of change
Approach
What is the motivation for this PR?
To fix
N/Acounters on management ports on Broadcom platforms.Work item tracking
How did you do it?
Temporarily fill in
0values for counters that are supported in the usual interfaces but not supported in the management ports.How did you verify/test it?
show interface countersno longer showN/Acounters.Any platform specific information?
Broadcom only.
Documentation