-
Notifications
You must be signed in to change notification settings - Fork 971
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
fix: enhanced FitError of JobInfo by logging the insufficient resources #3052
fix: enhanced FitError of JobInfo by logging the insufficient resources #3052
Conversation
Welcome @srikanth-iyengar! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…ent resources this will help in identifying reasons for insufficient resources Signed-off-by: Iyengar, Srikanth <[email protected]>
/hold |
Hi, @srikanth-iyengar , thanks for your hard work on this issue. Actually, the filter result is already exist and don't need to do any calculations. You can find out the first failed scheduling pod's message and append to the podgroup's message. Just like this highlight in picture: pod's message has been fixed in #3051. FYI. |
Something like this @lowang-bh ? |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
/close |
@lowang-bh: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
fix #2993