-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
argo watch does not update/refresh screen #2678
Comments
This maybe fixed in v2.7.2 CLI- can you please try that version? |
Just tried v2.7.2 CLI against v2.7.1 in cluster. Tomorrow I'll give it another shot also updating the workflow-controller to v2.7.2 |
Looking at the most recent code I notice it only updates when the workflow changed. So you should see a change every time a step changes state (e.g becomes complete) or the workflow changes state (e.g. completes). You should not expect it to just "update every few seconds" without a state change. |
Well, initially that's the impression that I had. However, it definitely does not refresh after a while, although the step changed state. I just tested with a workflow that finished little over 15min, however the |
Can you please provide an example of the workflow so I can try and repro? |
I have a potential fix, but I'm not greatly confident in it. I forgot to ask can you run |
I was able to reproduce with the following workflow: apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: dag-nested-
spec:
entrypoint: diamond
templates:
- name: echo
inputs:
parameters:
- name: message
container:
image: alpine:3.7
command: [sleep , 30]
- name: diamond
dag:
tasks:
- name: A
template: nested-diamond
arguments:
parameters: [{name: message, value: A}]
- name: B
dependencies: [A]
template: nested-diamond
arguments:
parameters: [{name: message, value: B}]
- name: C
dependencies: [A]
template: nested-diamond
arguments:
parameters: [{name: message, value: C}]
- name: D
dependencies: [B, C]
template: nested-diamond
arguments:
parameters: [{name: message, value: D}]
- name: nested-diamond
inputs:
parameters:
- name: message
dag:
tasks:
- name: A
template: echo
arguments:
parameters: [{name: message, value: "{{inputs.parameters.message}}A"}]
- name: B
dependencies: [A]
template: echo
arguments:
parameters: [{name: message, value: "{{inputs.parameters.message}}B"}]
- name: C
dependencies: [A]
template: echo
arguments:
parameters: [{name: message, value: "{{inputs.parameters.message}}C"}]
- name: D
dependencies: [B, C]
template: echo
arguments:
parameters: [{name: message, value: "{{inputs.parameters.message}}D"}] Below screenshot shows at the top the output of |
Are you using argo server? Any kind of ingress? Can I ask you to run with the |
Yes, we are running argo-server in client auth mode. Please find the last lines of the debug output here
|
Checklist:
What happened:
argo watch WORKFLOW_NAME
most of the time does not refresh it's outputWhat you expected to happen:
I expected argo watch to refresh it's output every few seconds as was the case with at least v2.4
How to reproduce it (as minimally and precisely as possible):
Submit a workflow and either add the '--watch' flag, or submit a workflow and execute the
argo watch WORKFLOW_NAME
afterwards.Anything else we need to know?:
Environment:
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: