Cronworkflow Using Forbid and specify the deadline will have problem

[whybeyoung]

Pre-requisites

• [X] I have double-checked my configuration
• [X] I can confirm the issues exists when I tested with :latest
• [ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?

Dear:

this is my case: we have many cron workflows . and we using the Forbid concurrency stragedy. however, when we specify the activeDeadlineSeconds options , if the workflow instance trigger the timeout ， it will leave the pod with DeadlineExceeded status. Then i want that forbid concurrency can ignore this DeadlineExceeded instance, and the cron scheduler continue the next run. (we can't use other stragedy because of some reasons) do you have some ideas? may be we should have a stragedy "ForbidIgnoreDeadline"？

Version

v3.3.10

Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

spec:
  activeDeadlineSeconds: 3600
  arguments:
    parameters:
    - name: hdfs_server
      value: nn002.bjb.hadoop:8020

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

[JPZ13]

@whybeyoung - Could you include the full workflow that reproduces the issue rather than a snippet of the workflow? We don't have quite enough information to understand the issue and reproduce without the full workflow

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity and needs more information. It will be closed if no further activity occurs.