-
Notifications
You must be signed in to change notification settings - Fork 769
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
[pretest] Testcase to validate backend acl load #12510
Conversation
Signed-off-by: Neetha John <[email protected]>
The test case looks good to me, but can we put the test case in the acl folder? It's because we usually put some utility function in pre test. |
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.
as comments
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
wanted to have this as a pretest check for backend testbed since all nightly runs depend on this acl being setup properly. |
I see. So if test |
Signed-off-by: Neetha John <[email protected]>
* Testcase to validate backend acl load Signed-off-by: Neetha John <[email protected]>
* Testcase to validate backend acl load Signed-off-by: Neetha John <[email protected]>
Cherry-pick PR to 202311: #12576 |
Cherry-pick PR to 202305: #12577 |
Testing was done against 202305 image on t0-backend and non t0-backend |
* Testcase to validate backend acl load Signed-off-by: Neetha John <[email protected]>
* Testcase to validate backend acl load Signed-off-by: Neetha John <[email protected]>
Description of PR
Summary:
Fixes #12048
Type of change
Back port request
Approach
What is the motivation for this PR?
Add an explicit testcase to validate that acl is loaded successfully on the backend T0 testbed. Without this case, acl load failure was determined by examining the nighly run failures on the backend testbed
How did you verify/test it?
Ran the test against a backend T0 testbed with the fix to load acl correctly and it passed
Ran the test against a non backend T0 testbed and it is skipped
Supported testbed topology if it's a new test case?
t0-backend