-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The pod exists in the cluster but log show "no artifact logs are available" #14083
Closed
4 tasks done
Labels
Comments
I found that it is related to the ARCHIVED status of the workflow. Only the display when ARCHIVED is true is abnormal. |
isubasinghe
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Jan 30, 2025
…Fixes: argoproj#14083 (argoproj#14087) Signed-off-by: shuangkun <tsk2013uestc@163.com>
isubasinghe
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Jan 30, 2025
…Fixes: argoproj#14083 (argoproj#14087) Signed-off-by: shuangkun <tsk2013uestc@163.com>
isubasinghe
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Jan 31, 2025
…Fixes: argoproj#14083 (argoproj#14087) Signed-off-by: shuangkun <tsk2013uestc@163.com>
4 tasks
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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 pod still exists in the cluster
but log shows "no artifact logs are available"

Version(s)
latest
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.
set persistence archive to true
submit workflow
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: