-
Notifications
You must be signed in to change notification settings - Fork 714
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TACACS+] Add TACACS per-command accounting test case. #4674
Merged
liuh-80
merged 49 commits into
sonic-net:master
from
liuh-80:dev/liuh/tacacs_accounting_ut
Jan 4, 2022
Merged
[TACACS+] Add TACACS per-command accounting test case. #4674
liuh-80
merged 49 commits into
sonic-net:master
from
liuh-80:dev/liuh/tacacs_accounting_ut
Jan 4, 2022
+701
−25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qiluo-msft
reviewed
Nov 20, 2021
qiluo-msft
reviewed
Nov 20, 2021
qiluo-msft
reviewed
Dec 9, 2021
tests/common/utilities.py
Outdated
@@ -39,6 +38,22 @@ def skip_release(duthost, release_list): | |||
if any(release == duthost.sonic_release for release in release_list): | |||
pytest.skip("DUT is release {} and test does not support {}".format(duthost.sonic_release, ", ".join(release_list))) | |||
|
|||
def check_skip_release(duthost, release_list): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
qiluo-msft
reviewed
Dec 11, 2021
tests/tacacs/utils.py
Outdated
duthost.shell("sudo config tacacs default passkey") | ||
duthost.shell("sudo config aaa authentication login default") | ||
duthost.shell("sudo config aaa authentication failthrough default") | ||
|
||
(skip, reason) = check_skip_release(duthost, per_command_check_skip_versions) | ||
if skip: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
qiluo-msft
reviewed
Dec 11, 2021
qiluo-msft
previously approved these changes
Dec 13, 2021
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
# Conflicts: # tests/kvmtest.sh # tests/tacacs/utils.py
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
qiluo-msft
approved these changes
Jan 4, 2022
5 tasks
yutongzhang-microsoft
added a commit
that referenced
this pull request
Aug 31, 2022
…running. (#6246) Description of PR During the module test_accounting.py running, it sets tacacs accounting in config db, which will add the key AAA and TACPLUS in config db. This cause the inconsistent in config db before and after the test case running. In this pr, we delete the key AAA and TACPLUS in config db after the module running. Summary: Fixes # (#4674) What is the motivation for this PR? During the module test_accounting.py running, it sets tacacs accounting in config db, which will add the key AAA and TACPLUS in config db. This cause the inconsistent in config db before and after the test case running. In this pr, we delete the key AAA and TACPLUS in config db after the module running. How did you do it? Use configlet to delete the config after test case running. How did you verify/test it? Check the config db before and after the test case running. Signed-off-by: Yutong Zhang <yutongzhang@microsoft.com>
wangxin
pushed a commit
that referenced
this pull request
Sep 6, 2022
…running. (#6246) Description of PR During the module test_accounting.py running, it sets tacacs accounting in config db, which will add the key AAA and TACPLUS in config db. This cause the inconsistent in config db before and after the test case running. In this pr, we delete the key AAA and TACPLUS in config db after the module running. Summary: Fixes # (#4674) What is the motivation for this PR? During the module test_accounting.py running, it sets tacacs accounting in config db, which will add the key AAA and TACPLUS in config db. This cause the inconsistent in config db before and after the test case running. In this pr, we delete the key AAA and TACPLUS in config db after the module running. How did you do it? Use configlet to delete the config after test case running. How did you verify/test it? Check the config db before and after the test case running. Signed-off-by: Yutong Zhang <yutongzhang@microsoft.com>
Azarack
pushed a commit
to Azarack/sonic-mgmt
that referenced
this pull request
Oct 17, 2022
…running. (sonic-net#6246) Description of PR During the module test_accounting.py running, it sets tacacs accounting in config db, which will add the key AAA and TACPLUS in config db. This cause the inconsistent in config db before and after the test case running. In this pr, we delete the key AAA and TACPLUS in config db after the module running. Summary: Fixes # (sonic-net#4674) What is the motivation for this PR? During the module test_accounting.py running, it sets tacacs accounting in config db, which will add the key AAA and TACPLUS in config db. This cause the inconsistent in config db before and after the test case running. In this pr, we delete the key AAA and TACPLUS in config db after the module running. How did you do it? Use configlet to delete the config after test case running. How did you verify/test it? Check the config db before and after the test case running. Signed-off-by: Yutong Zhang <yutongzhang@microsoft.com>
allen-xf
pushed a commit
to allen-xf/sonic-mgmt
that referenced
this pull request
Oct 28, 2022
…running. (sonic-net#6246) Description of PR During the module test_accounting.py running, it sets tacacs accounting in config db, which will add the key AAA and TACPLUS in config db. This cause the inconsistent in config db before and after the test case running. In this pr, we delete the key AAA and TACPLUS in config db after the module running. Summary: Fixes # (sonic-net#4674) What is the motivation for this PR? During the module test_accounting.py running, it sets tacacs accounting in config db, which will add the key AAA and TACPLUS in config db. This cause the inconsistent in config db before and after the test case running. In this pr, we delete the key AAA and TACPLUS in config db after the module running. How did you do it? Use configlet to delete the config after test case running. How did you verify/test it? Check the config db before and after the test case running. Signed-off-by: Yutong Zhang <yutongzhang@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of PR
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
Add new E2E test case to cover user scenarios.
How did you verify/test it?
Run new UT make sure they are all pass.
Make sure all current UT not break during merge validation.
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
Documentation
https://github.com/Azure/SONiC/blob/master/doc/aaa/TACACS%2B%20Design.md