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.

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

The pod exists in the cluster but log show "no artifact logs are available" #14083

Closed
4 tasks done
shuangkun opened this issue Jan 15, 2025 · 1 comment · Fixed by #14087
Closed
4 tasks done

The pod exists in the cluster but log show "no artifact logs are available" #14083

shuangkun opened this issue Jan 15, 2025 · 1 comment · Fixed by #14087

Comments

@shuangkun
Copy link
Member

shuangkun commented Jan 15, 2025

Pre-requisites

  • I have double-checked my configuration
  • I have tested with the :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.
  • I have searched existing issues and could not find a match for this bug
  • I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?

The pod still exists in the cluster

upgrade % kubectl get pod -n argo | grep wf
hello-world-wfpfz               0/2     Completed   0          18h

but log shows "no artifact logs are available"
Image

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

  persistence: |
    connectionPool:
      maxIdleConns: 100
      maxOpenConns: 0
      connMaxLifetime: 0s # 0 means connections don't have a max lifetime
    archiveTTL: 30d
    archive: true

submit workflow

apiVersion: argoproj.io/v1alpha1
kind: Workflow                  # new type of k8s spec.
metadata:
  generateName: hello-world-    # name of the workflow spec.
spec:
  entrypoint: main          # invoke the main template.
  templates:
    - name: main              # name of the template.
      container:
        image: busybox:latest
        command: [ echo ]
        args: [ "hello world" ]
      initContainers:
      - name: hello
        image: busybox:latest
        command: ["echo", "hello"]
        mirrorVolumeMounts: true

Logs from the workflow controller

kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

Logs from in your workflow's wait container

kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded
@shuangkun
Copy link
Member Author

I found that it is related to the ARCHIVED status of the workflow. Only the display when ARCHIVED is true is abnormal.

@tczhao tczhao closed this as completed in b1a65e7 Jan 15, 2025
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>
isubasinghe pushed a commit that referenced this issue Jan 31, 2025
…Fixes: #14083 (#14087)

Signed-off-by: shuangkun <tsk2013uestc@163.com>
isubasinghe pushed a commit that referenced this issue Jan 31, 2025
…Fixes: #14083 (#14087)

Signed-off-by: shuangkun <tsk2013uestc@163.com>
Joibel pushed a commit that referenced this issue Feb 7, 2025
…Fixes: #14083 (#14087)

Signed-off-by: shuangkun <tsk2013uestc@163.com>
(cherry picked from commit b1a65e7)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant