Fix KeyError: u'MUX_LINKMGR' when comparing pre config and current config#6918
Conversation
…nfig Signed-off-by: Zhaohui Sun <zhaohuisun@microsoft.com>
|
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
…nfig (#6918) What is the motivation for this PR? Some test cases failed at teardown when comparing pre config and current config: for key in cur_config_extra_keys: > cur_only_config[duthost.hostname].update({key: cur_running_config[key]}) E KeyError: u'MUX_LINKMGR' The issue is introduced by #6527. How did you do it? Get previous and current config keys after removing exclusive keys. Also add [cfg_context] for cur_only_config and pre_only_config How did you verify/test it? Run dualtor case,such as dualtor/test_tor_ecn.py::test_dscp_to_queue_during_encap_on_standby Signed-off-by: Zhaohui Sun <zhaohuisun@microsoft.com>
Signed-off-by: Zhaohui Sun zhaohuisun@microsoft.com
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Some test cases failed at teardown when comparing pre config and current config:
The issue is introduced by #6527.
How did you do it?
Get previous and current config keys after removing exclusive keys.
Also add [cfg_context] for cur_only_config and pre_only_config
How did you verify/test it?
Run dualtor case,such as
dualtor/test_tor_ecn.py::test_dscp_to_queue_during_encap_on_standbyAny platform specific information?
Supported testbed topology if it's a new test case?
Documentation