Skip to content

[Bug] [Service/Master] Global variables of sub-workflows not getting inherited by underlying sub-workflows #17534

@MSerCegeka

Description

@MSerCegeka

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

After the upgrade from 3.2.2 to 3.3.1, most of our workflows stopped working due to missing variables. This is due to global parameters from sub-workflows not being correctly set for use within their underlying sub-workflows.

What you expected to happen

When setting a global parameter in a sub-workflow, it's values should be propagated to all underlying sub-workflows.

How to reproduce

Create the following situation/workflow:

  • Workflow A calls Workflow B as a sub-workflow
  • Workflow B calls Workflow C as a sub-workflow
  • Workflow B defines a global variable $VALUE
  • Workflow C contains a shell script to print the $VALUE value
  • If you start execution from Workflow A, Workflow C does not receive the global $VALUE from Workflow B and prints nothing

Anything else

No response

Version

3.3.1

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions