-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman play kube --replace : timeout #12039
Comments
Is that remote only? |
It seems to be. Here are the logged failures since my initial report: Podman play kube [It] podman play kube replace
From that list I removed this one because it looks like a timeout fetching from k8s.io. That suggested that this bug might just be that timeout, misreported in the remote client, but the failure yesterday (in a PR that, presumably, includes #12280) implies otherwise. |
Did it happen again? |
Only two instances since my last post: Podman play kube [It] podman play kube replace
|
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
@edsantiago Still an issue? |
Twice in the last month: Podman play kube [It] podman play kube replace
|
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
@edsantiago have you seen this happen again recently? |
Last one in my logs is 05-23. |
That is good enough for me to close it. We fixed some deadlocks in the recent past, so it may be related. Let's reopen if it pops up again. |
Only one logged flake, but I've seen this one multiple times in the last two days on other PRs:
Podman play kube [It] podman play kube replace
The text was updated successfully, but these errors were encountered: