Skip to content
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.

Sign up for GitHub

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

Jump to bottom

--wait flag sometimes misses pods #19288

Open
spowelljr opened this issue Jul 18, 2024 · 3 comments · Fixed by #19748 · May be fixed by #20315
Open

--wait flag sometimes misses pods #19288

spowelljr opened this issue Jul 18, 2024 · 3 comments · Fixed by #19748 · May be fixed by #20315
Assignees
@ComradeProgrammer
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@spowelljr
Copy link
Member

spowelljr commented Jul 18, 2024 •
edited
Loading

I was experimenting with the --wait=all command and found the that implementation grabs a list of the pods and then waits for them to be healthy, however, sometimes the list of pods is pulled before some of the pods have even been created, resulting in them not being in the waiting check. For example I had a run where the wait returned quickly, but after running kubectl get pods -A I could see that the coredns pod was just created and was not ready.
@spowelljr
Copy link
Member Author 

kube-system   coredns-7c65d6cfc9-5vgs2           1/1     Running   0          12s
kube-system   etcd-minikube                      1/1     Running   0          18s
kube-system   kube-apiserver-minikube            1/1     Running   0          18s
kube-system   kube-controller-manager-minikube   1/1     Running   0          18s
kube-system   kube-proxy-9q82q                   1/1     Running   0          13s
kube-system   kube-scheduler-minikube            1/1     Running   0          18s

@ComradeProgrammer ComradeProgrammer self-assigned this Oct 2, 2024
@ComradeProgrammer ComradeProgrammer mentioned this issue Oct 3, 2024
Merged
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2024
This was referenced Jan 25, 2025
Merged
Open
@prezha prezha reopened this Jan 26, 2025
@prezha
Copy link
Contributor

prezha commented Jan 26, 2025

there's a pr #20315 that should fix this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ComradeProgrammer ComradeProgrammer

Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
5 participants
@prezha @k8s-ci-robot @spowelljr @ComradeProgrammer @k8s-triage-robot