Logs API Stops Functioning When a Pod Fails #21286
Labels
bug
Something isn't working
component:api
API bugs and enhancements
version:EOL
Latest confirmed affected version has reached EOL
Checklist:
argocd version
.Describe the bug
When a pod in a deployment fails, the logs API returns a 500 status code when attempting to fetch logs for the entire deployment. This behavior has been observed when one or more pods are in one of the following states: Completed, Failed, or Error.
To Reproduce
Deploy this chart https://github.com/Fluder-Paradyne/hello-world-helm/tree/main/charts/hello-world
and run this command, this cmd will cause the pod to run out off storage and get evicted.
Kubernetes logs api gives ,
unable to retrieve container logs for containerd://a0002996fc1eb2a973c4708fa4f4f5f1b9e643114322c71fe54dbbfef27148d5
This causes a parsing error here
Expected behavior
Show logs of other pods
Screenshots
Version
Logs
The text was updated successfully, but these errors were encountered: