-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Description
Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
I have a DAG making use of global artifacts. However some steps do not see the results that previous dependent steps did to that global artifact.
This is how my workflow looks like:
The Prepare
step produces an artifact named kubeconfigs
.
The create-shoot-xxx
step overwrites/updates that artifact.
The 4 parallel steps at the bottom of the graph all use the artifcat kubeconfigs
. However some of them see the artifact state that was produced by Prepare
(e.g. step e2e-fast
), while others (e.g. step plant-test
) see the expected one that was produced by create-shoot-xxx
.
I've attached the resulting workflow resource (albeit it's big...):
workflow.yaml.zip
From the status
field I can see that:
Prepare
step outputs at artifact key ...live-cron-gcp-z92nr-wf-445938729/kubeconfigs.tgz
create-shoot
step outputs at artifact key ...live-cron-gcp-z92nr-wf-3855664820/kubeconfigs.tgz
plant-test
correctly inputs with artifact key ...live-cron-gcp-z92nr-wf-3855664820/kubeconfigs.tgz
e2e-fast
wrongly inputs with artifact key ...live-cron-gcp-z92nr-wf-445938729/kubeconfigs.tgz
Maybe this one here is similar to #1085 (but not the same as I'm running the latest argo version 2.3.0-rc3)
What you expected to happen:
All 4 parallel steps at the bottom must see the artifact as produced by step create-shoot-xxx
Environment:
- Argo version:
2.3.0-rc3
- Kubernetes version :
1.14.0