-
Notifications
You must be signed in to change notification settings - Fork 807
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 Three Papercuts #1933
Fix Three Papercuts #1933
Conversation
…s invalid Signed-off-by: Connor Catlett <[email protected]>
Code Coverage DiffThis PR does not change the code coverage |
/retest |
Signed-off-by: Connor Catlett <[email protected]>
Signed-off-by: Connor Catlett <[email protected]>
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 now, thanks for the papercut fixes!
/retest |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Is this a bug fix or adding new feature?
Bug fix
What is this PR about? / Why do we need it?
Fixes three small papercuts (each in their own commit):
Fix kops clusters becoming stuck when local KUBECONFIG is invalid
When the local kubeconfig represents a cluster that no longer exists, patching (and thus creating) a kops-based cluster will get stuck. This fixes that by explcitly setting the config for patch operations to
/dev/null
Restrain
shfmt
tohack/
directoryshfmt
was trying to modify scripts in thevenv
inbin/
, sometimes causingmake verify/update
to fail locally.Attempt to delete Prow clusters that fail to create
We already delete clusters where the e2e tests fail (as of #1856), but leave behind clusters where creation failed.
What testing is done?
Manual/CI