Open Iqqdd99 opened 1 month ago
651e199a20c96319c4bd9d24c084a1de9f2e62725749a9f239adfb785147299b
That commit SHA 404s for this repo: https://github.com/argoproj/argo-workflows/commit/651e199a20c96319c4bd9d24c084a1de9f2e62725749a9f239adfb785147299b
< Grpc-Metadata-Content-Type: application/grpc
argo
use grpc client, this is the interface of grpc protocol
argo-server seems compatible with both http and grpc, and /api/v1/workflows/{namespace}
seems to work fine
I believe this requires ?logOptions.container=main
or another container
selection
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
The endpoint
/api/v1/workflows/{namespace}/{name}/log
doesn't work, it returns an empty response.The argo CLI works:
The data of the workflow can be accessed using the API REST
/api/v1/workflows/{namespace}/{name}
:But
/api/v1/workflows/{namespace}/{name}/log
gives an empty responseVersion(s)
sha256:651e199a20c96319c4bd9d24c084a1de9f2e62725749a9f239adfb785147299b
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container