-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 some diagnostic error handling (NetworkCheck and DiagnosticPod) #16848
Fix some diagnostic error handling (NetworkCheck and DiagnosticPod) #16848
Conversation
When the check can't run because the cluster is an all-in-one, this shouldn't give a warning. Now it's an info. It would be nice to put this in CanRun so the skip can be a Note but given checking for the condition can raise its own error, it seemed wisest to leave it until the diagnostic is running.
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pravisankar, sosiouxme The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
flakes |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
Automatic merge from submit-queue (batch tested with PRs 16848, 16874). |
Fixes #16847
A keyboard interrupt on the NetworkCheck diagnostic will actually abort it (giving it a chance to clean up) and proceed to the next diagnostic.
The same is done for DiagnosticPod (which previously did not catch the signal and cleanup at all).