-
Notifications
You must be signed in to change notification settings - Fork 137
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-2575] Clarify error returned by IsPodFitNode #824
Conversation
IsPodFitNode should clearly set the error if the pod or node is missing from the cache when run. The result, if it is an error, contains the predicate plugin name that failed to improve identification in the events.
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.
+1 LGTM (pending e2e test runs).
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #824 +/- ##
==========================================
- Coverage 66.13% 66.05% -0.08%
==========================================
Files 69 69
Lines 7517 7523 +6
==========================================
- Hits 4971 4969 -2
- Misses 2334 2342 +8
Partials 212 212 ☔ 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.
@wilfred-s nice patch! a couple of comments left. PTAL
Logged YUNIKORN-2578 for that as I noticed the same. Also logged YUNIKORN-2577 to clean up the IsPodFitNodeViaPreemption function |
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.
LGTM
What is this PR for?
IsPodFitNode should clearly set the error if the pod or node is missing from the cache when run. The result, if it is an error, contains the predicate plugin name that failed to improve identification in the events.
What type of PR is it?
What is the Jira issue?
How should this be tested?
NA, no behaviour change just cleanup of return values