Ignore Port Counter laganalyzer error in test_iface_namingmode #16073
Conversation
Similar issue to sonic-net#12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process. Adding a loganalyzer ignore for this message to this test to fix.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/Azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/Azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/Azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/Azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@kenneth-arista , @veronica-arista please help to get the build passed? thanks |
|
/Azp run Azure.sonic-mgmt |
|
Commenter does not have sufficient privileges for PR 16073 in repo sonic-net/sonic-mgmt |
|
/Azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
The failure appears to be build pipeline specific. For example, see https://elastictest.org/scheduler/publictestplan/67883a3846e46d15f7487fec. The problem is that |
|
@arlakshm please help? |
|
/Azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@LinJin23 , would you please help on this one? |
|
Hi @veronica-arista , could you sync the latest sonic-net:master branch, merge it into branch veronica-arista:master-fix-loganalyzer-test_iface_namin, and push the changes again? The outdated sonic-net:master branch seems to be affecting the pipeline display. |
…lyzer-test_iface_namin
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Similar issue to sonic-net#12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process. Adding a loganalyzer ignore for this message to this test to fix.
Description of PR
Summary:
Loganalyzer error
ERR syncd#syncd: :- collectData: Failed to get stats of Port Counterin test_iface_namingmode.Similar issue to #12174 in that counters stats continue to be polled in an unstable state. In the test_iface_namingmode.py case, TestConfigInterface resets the interface configurations at the end, and these syslog errors only appear after the test begins the teardown process.
Adding a loganalyzer ignore for this message to this test, since we observe this error only with test_iface_namingmode.
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Confirmed this resolved test_iface_namingmode fails on our t2 testbed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation