-
Notifications
You must be signed in to change notification settings - Fork 38.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
rkt: return non error if the pod doesn't exist in GetPodStatus() #14706
Conversation
Previously, GetPodStatus() will return error if the pod is never created. However we've never seen the sync loop fail because in the beginning of the loop, if the pod is not found, it will be created. This works fine except the pod that keeps crashing. Because the above logic will keep restarting the pod as if it's never created. This PR fixes the bug.
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
Labelling this PR as size/S |
This makes the code behaves more like the docker counterpart.. :) |
@k8s-bot ok to test |
Unit, integration and GCE e2e test build/test passed for commit 4309caf. |
Unit, integration and GCE e2e test build/test passed for commit 4309caf. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Unit, integration and GCE e2e build/test failed for commit 4309caf. |
rkt is not tested in e2e yet. |
Anyway will need to rebase after #14686 |
Automatic merge from submit-queue |
Auto commit by PR queue bot
Previously, GetPodStatus() will return error if the pod is never
created. However we've never seen the sync loop fail because in the
beginning of the loop, if the pod is not found, it will be created.
This works fine except the pod that keeps crashing. Because the above
logic will keep restarting the pod as if it's never created.
This PR fixes the bug.
/cc @dchen1107 @yujuhong