-
Notifications
You must be signed in to change notification settings - Fork 141
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
[YUNIKORN-1956] Add wildcard user/group limit e2e tests #738
Conversation
Signed-off-by: PoAn Yang <payang@apache.org>
Signed-off-by: PoAn Yang <payang@apache.org>
671b243
to
ec57ad7
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #738 +/- ##
==========================================
- Coverage 69.52% 69.46% -0.07%
==========================================
Files 50 50
Lines 7993 7993
==========================================
- Hits 5557 5552 -5
- Misses 2248 2252 +4
- Partials 188 189 +1 ☔ View full report in Codecov by Sentry. |
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.
looks good.
ginkgo.By("Update config") | ||
annotation = "ann-" + common.RandSeq(10) | ||
// The wait wrapper still can't fully guarantee that the config in AdmissionController has been updated. | ||
yunikorn.WaitForAdmissionControllerRefreshConfAfterAction(func() { |
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.
Why is it so? If it is known issue, Do we have any jira to track this? I remember some one else too raised this issue.
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.
I think this is introduced from https://issues.apache.org/jira/browse/YUNIKORN-1998. I just copy-paste from previous test cases.
What is this PR for?
Specific user/group limits + wild card user/group limits to ensure order of precedence:
5a) When the user limit is specified, it should be considered for that specific user
5b) When the user limit is not specified, the wild card user limit should be considered for that specific user
6a) When the group limit is specified, it should be considered for that specific group
6b) When the group limit is not specified, the wild card group limit should be considered for that specific group
What type of PR is it?
What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1956