You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The workflow controller panics (and crashes) when running the hello-world workflow when following the getting started instructions with argo 2.5.0-rc2. IMHO it should support an empty configmap, falling back to sensible defaults.
How to reproduce it (as minimally and precisely as possible):
$ minikube version
minikube version: v1.6.2
commit: 54f28ac5d3a815d1196cd5d57d707439ee4bb392
$ minikube start
(new kube 1.17 cluster gets created with kvm2 on linux)
$ kubectl create ns argo
$ kubectl apply -n argo -f https://raw.githubusercontent.com/argoproj/argo/v2.5.0-rc1/manifests/install.yaml
$ argo submit --watch https://raw.githubusercontent.com/argoproj/argo/master/examples/hello-world.yaml
Anything else we need to know?:
The panic happens here. It's because the wfArchive of the WorkflowController is nil. It seems that the assumption is that the config key in the workflow-controller-configmapshould always exist and in this case it does not, so it never instantiates the wfArchive in the WorkflowController.updateConfig method.
Environment:
Argo version:
This is argo v2.5.0-rc2, seems the version info of the downloaded binary is empty:
Checklist:
What happened:
The workflow controller panics (and crashes) when running the hello-world workflow when following the getting started instructions with
argo 2.5.0-rc2
. IMHO it should support an empty configmap, falling back to sensible defaults.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The panic happens here. It's because the
wfArchive
of theWorkflowController
is nil. It seems that the assumption is that theconfig
key in theworkflow-controller-configmap
should always exist and in this case it does not, so it never instantiates thewfArchive
in theWorkflowController.updateConfig
method.Environment:
This is argo v2.5.0-rc2, seems the version info of the downloaded binary is empty:
Other debugging information (if applicable):
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: