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 workflows.argoproj.io/actor-email is different between stop and resume workflow #14121

Open
4 tasks done
tczhao opened this issue Jan 24, 2025 · 0 comments · May be fixed by #14122
Open
4 tasks done

The workflows.argoproj.io/actor-email is different between stop and resume workflow #14121

tczhao opened this issue Jan 24, 2025 · 0 comments · May be fixed by #14122
Labels

Comments

@tczhao
Copy link
Member

tczhao commented Jan 24, 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?

Resuming a workflow gives us the following label

workflows.argoproj.io/actor-email: admin.at.your.org
workflows.argoproj.io/creator-email: admin.at.your.org

Suspend a workflow gives us the following label

workflows.argoproj.io/actor-email: admin-your.org
workflows.argoproj.io/creator-email: admin.at.your.org

The actor-email label should be consistent

Version(s)

latest (7305c18)

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.

.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant