Test PG counters is accurate when using create_only_config_db_buffers… #1
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.
… optimization
Description of PR
This test is checking that PG counters inside snmp docker are accurate when using create_only_config_db_counters optimization.
Summary:
Fixes sonic-net/sonic-buildimage#17448 and is related to the fix, available in sonic-net/sonic-snmpagent#303
Type of change
Back port request
Approach
What is the motivation for this PR?
To enhance the bug fix mentioned above solving an issue with PG counters optimization.
How did you do it?
How did you verify/test it?
Run the test multiple times on various setups.
Any platform specific information?
Test assumes unicast only
Supported testbed topology if it's a new test case?
Documentation