argo-workflows icon indicating copy to clipboard operation
argo-workflows copied to clipboard

Linting/Submission for Workflow Of Workflows not working for workflows steps withItems and other complex workflows.

Open deepaksinghvi opened this issue 2 years ago • 0 comments

Checklist

  • [x] Double-checked my configuration.
  • [X] Tested using the latest version.
  • [x] Used the Emissary executor.

Summary

Linting/Submission for Workflow Of Workflows not working for workflows steps withItems and other complex workflows.

What happened/what you expected to happen? Would like to use workflow of workflow feature of ArgoWorkflow but it is working for basic cases only.

Three cases for details on the issue:

  1. Used simple hello world workflow as the json in parent workflow. Its working fine and NOT getting error

Used child workflow definition from here: https://argoproj.github.io/argo-workflows/walk-through/hello-world/

Workflow available in gist litn_working_helloworld_case.json https://gist.github.com/deepaksinghvi/75f00f51b08c7cf16ce57e19c139251a

  1. Used DAG child workflow as the json in parent workflow and getting error

    ✖ in "e62f9d660a864699a544cd94ff4f3cca" (Workflow): templates.main.tasks.workload8d53692805c748dda1aba1ebd622c78f templates.workload8d53692805c748dda1aba1ebd622c78f: failed to resolve {{inputs.parameters.message}}

Used child workflow definition from here: https://argoproj.github.io/argo-workflows/walk-through/dag/

Workflow available in gist litn_not_working_dag_case.json https://gist.github.com/deepaksinghvi/75f00f51b08c7cf16ce57e19c139251a

  1. Used Step witItems child workflow as the json in parent workflow and getting error

    ✖ in "e62f9d660a864699a544cd94ff4f3cca" (Workflow): templates.main.tasks.workload8d53692805c748dda1aba1ebd622c78f templates.workload8d53692805c748dda1aba1ebd622c78f: failed to resolve {{item.image}}

Used child workflow definition from here: https://argoproj.github.io/argo-workflows/walk-through/loops/

Workflow available in gist litn_not_working_withItems_case.json https://gist.github.com/deepaksinghvi/75f00f51b08c7cf16ce57e19c139251a

What version are you running? 3.2/3.3 both.

Diagnostics

Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.


# Logs from the workflow controller:
kubectl logs -n argo deploy/workflow-controller | grep ${workflow} 

# If the workflow's pods have not been created, you can skip the rest of the diagnostics.

# The workflow's pods that are problematic:
kubectl get pod -o yaml -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

# Logs from in your workflow's wait container, something like:
kubectl logs -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

deepaksinghvi avatar Aug 07 '22 12:08 deepaksinghvi