-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 wait for terminated pods or for minion nodes in the just-restarted cluster #11106
Closed
Closed
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
ad63780
fix wait for pods that are terminated
prezha 2c43003
bump kindnet
prezha 4dc4690
update containerd config: use CNIConfDir
prezha da8eba6
update crio config: use CNIConfDir
prezha a97accd
move setCNIConfDir logic to cni package
prezha bef7f54
fix crio
prezha f12e4c8
wait-less
prezha c16f005
bump the timeout from 70 to 90 mins
prezha b9d6ede
clean up /tmp
prezha 69dcc83
consolidate crs iface for cni net conf
prezha 49734db
clean up kvm
prezha 0b5acba
multinode: recommend kindnet over (incompatible) bridge
prezha ac40967
fix crio (again)
prezha 357b593
split other changes into separate prs
prezha File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
how about instead of waiting till it fails and then check the error message to see if it is a "Termianted pod" how about at beggning only range through pods which are not Terminated ?
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.
or as @ilya-zuyev noted
for _, pod := range pods.Items {
might have a condition we could checkThere 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 something like that (ie, 'skipping!') was my original intention:
minikube/pkg/minikube/bootstrapper/bsutil/kverify/pod_ready.go
Lines 137 to 139 in 357b593
but it somehow got lost along the way (when i also added host checking)
i'll have a look...
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.
@medyagh @ilya-zuyev thanks for catching this!
it shouldn't have waited on non-running and non-pending pods because of:
minikube/pkg/minikube/bootstrapper/bsutil/kverify/pod_ready.go
Lines 137 to 139 in 357b593
and
minikube/pkg/minikube/bootstrapper/bsutil/kverify/pod_ready.go
Lines 105 to 108 in 357b593
then
minikube/pkg/minikube/bootstrapper/bsutil/kverify/pod_ready.go
Lines 116 to 118 in 357b593
would exit immediately (due to the returned error from checkCondition()), but i've missed that specific one in:
minikube/pkg/minikube/bootstrapper/bsutil/kverify/pod_ready.go
Lines 72 to 73 in 357b593
so i've corrected that in 6779c72 in #11209 to test it there first
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.
@ilya-zuyev @medyagh actually, this was ok - no need to change anything here as
wait
works as intended (it will skip if pod is gone or if the just-restarted-minion node is not yet ready (detailed explanation above still holds)i'll close this one in favour of #11209
/close