[copp] Update the way copp config is applied in test_copp #4595
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.
Signed-off-by: Andrii-Yosafat Lozovyi andrii-yosafatx.lozovyi@intel.com
Description of PR
Summary: test_copp.py started to fail after
SONiC.master.43510-dirty-20211014.091725
because new COPP config wasn't applied on DUT, this happened due to recent PR - 8969 that binded copp-config.service to sonic.target.In order to apply new COPP config
copp_cfg.j2
file should be edited. This PR will updated the way COPP config is applied in test_copp.py.Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Update the way COPP config is applied in TC due to recent changes in - 8969
How did you do it?
How did you verify/test it?
Run test_copp.py on
SONiC.master.43510-dirty-20211014.091725
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation