New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLI] --watch option does not work when using --instanceid & unable to list workflows #3229
Comments
Are you testing out Argo? Can I recommend you start with the quick start manifests? (Look in |
I also note you're using an old version of the UI. Pre v2.8. This is probably a bug in the Helm chart you may wish to raise with that team. |
Hello, I am trying to automate argo helm installation using argocd and was trying to install the helm chart manually first to figure out what values might need to be overridden |
I tried the latest images too, and run into the same issue. I will raise an issue in the argo helm repo. |
@alexec Why does this fail, do I need to enable TLS? |
I am able to reproduce this issue even by using the manifests. There is an existing argo installation in my cluster, deployed using the helm charts. It's controller is setup to look for workflows in only a specific namespace (controller configmap has the namespace entry) I have installed argo stable using the manifests provided into another namespace "argo"
I have setup a serviceaccount workflow with necessary permissions. I edited the workflow controller config map and added the following lines and deleted the controller pod so that the changes take effect
Then i tried, Cli output gets stuck with Name: build-deploy-model-l65qz |
1 similar comment
This has been fixed in v2.9, but this has not been released yet. |
You must pass |
Checklist:
What happened:
I have done the following to setup argo workflow with instanceid:
a) Setup a serviceaccount "workflow", rbac Role and Rolebinding
b) Installed argo using the helm chart from https://github.com/argoproj/argo-helm/tree/master/charts/argo
c) submitted a job by specifying the --instanceid and --watch option
d) cli is indefinitely stuck, does not show the steps/status
e) argo list shows empty results possibly because there is another argo installation in a different namespace and I am not sure if cli is somehow connecting to that. I have exposed argo via ingress, Tried setting server:host as :80 but that did not work
What you expected to happen:
a) argo submit with --instanceid and --watch should show the status of each step in the workflow
b) I should be able to use argo list to list the workflows and then use argo get to see the workflow status
How to reproduce it (as minimally and precisely as possible):
a) Create rbac roles
b) Install argo using helm chart:
helm install ./argo --name argo-wf --set controller.instanceID.enabled=true --set controller.instanceID.useReleaseName=true --set controller.workflowNamespaces\[0\]=argo-wf --set controller.containerRuntimeExecutor=k8sapi --set singlenamespace=true --set init.serviceAccount=workflow --set minio.install=true --set installCRD=true --set server.ingress.enabled=true --set server.ingress.hosts\[0\]=argo.<clusterdomain> --set minio.ingress.enabled=true --set minio.ingress.hosts\[0\]=argo-minio.<cluster-domain> --namespace argo-wf --debug
c) Submit any workflow with instanceid and serviceaccount, though you can see steps running in the ui, the cli is stuck even when workflow is completed
d) In another terminal, I tried to list the workflows
Anything else we need to know?:
I am not sharing the workflow details, as on the UI it is showing that workflow ran successfully
I have attached UI screenshot
Environment:
Other debugging information (if applicable):
On submitting with verbose option I can see that CLI gets stuck at
DEBU[0002] Piping events to channel
and repeatedly printslevel=info msg="Re-establishing workflow watch"
Argo Server Pod logs
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: