Skip to content
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 UI: Unknown error #4714

Closed
tvalasek opened this issue Dec 11, 2020 · 8 comments · Fixed by #4741
Closed

Argo UI: Unknown error #4714

tvalasek opened this issue Dec 11, 2020 · 8 comments · Fixed by #4741
Assignees
Labels
solution/workaround There's a workaround, might not be great, but exists type/bug

Comments

@tvalasek
Copy link
Contributor

Summary

When using the UI I randomly get:

Unknown error. Open your browser error console for more information.:  Reload 8s`

Reload button is dead.

Browser error console shows:

2:2746/api/v1/workflow-events/test-argo-2-12?listOptions.fieldSelector=metadata.name=create-6w7w2:1 GET http://internal-XXXXXXXXXXXXXXX.us-west-2.elb.amazonaws.com:2746/api/v1/workflow-events/test-argo-2-12?listOptions.fieldSelector=metadata.name=create-6w7w2 net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK)

Diagnostics

What Kubernetes provider are you using?

AWS EKS v1.15.12-eks-31566f

What version of Argo Workflows are you running?

v2.12.0-rc5

OS and browser details:

Vivaldi 3.4.2066.106 (Stable channel) (x86_64)
Revision 9faa7da6e287d30fe3948ac5d9d62aefe7977da5
OS macOS Version 10.15.7 (Build 19H15)
JavaScript V8 8.6.395.25

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@alexec
Copy link
Contributor

alexec commented Dec 11, 2020

Do you have an ingress or proxy in front of your server? If so, please check its configuration wrt to keep-alives.

@tvalasek
Copy link
Contributor Author

i can do. i have a question though - something in this release that would trigger this behaviour? I'm using v2.9.5 in exactly same setup and that works just fine.

@alexec alexec self-assigned this Dec 11, 2020
@alexec
Copy link
Contributor

alexec commented Dec 11, 2020

Can you try :latest and see if you have the same problem?

@tvalasek
Copy link
Contributor Author

tvalasek commented Dec 11, 2020

ehm, with :latest I can't even get the workflow-controller pod running

kg po -n argo
NAME                                   READY   STATUS             RESTARTS   AGE
argo-server-698f5b9777-p8npw           1/1     Running            0          6m45s
workflow-controller-8457b7bf64-phnrz   1/1     Running            0          4h5m
workflow-controller-ffd5db46d-l76lb    0/1     CrashLoopBackOff   1          9s

no obvious reason, no logs :(

back to :v2.12.0-rc5 tag, all good:

kg po -n argo
NAME                                   READY   STATUS    RESTARTS   AGE
argo-server-6cff7b6f7b-j2lhn           1/1     Running   0          54s
workflow-controller-8457b7bf64-qb6xc   1/1     Running   0          53s

@alexec
Copy link
Contributor

alexec commented Dec 11, 2020

ah - I should have just said - just run the argocli, not the controller (which is broken)

@tvalasek
Copy link
Contributor Author

tried following setup

argocli:latest
argoexec:v2.12.0-rc5
workflow-controller:v2.12.0-rc5

Still receiving same error. I tried Chrome as well (just in case), same thing

@alexec
Copy link
Contributor

alexec commented Dec 11, 2020

If you reload the page it goes away?

@tvalasek
Copy link
Contributor Author

yes

@alexec alexec added solution/workaround There's a workaround, might not be great, but exists epic/unity labels Dec 11, 2020
alexec added a commit to alexec/argo-workflows that referenced this issue Dec 14, 2020
Signed-off-by: Alex Collins <alex_collins@intuit.com>
@alexec alexec closed this as completed in 2e278b0 Dec 15, 2020
@alexec alexec linked a pull request Dec 17, 2020 that will close this issue
1 task
@simster7 simster7 mentioned this issue Dec 17, 2020
9 tasks
simster7 pushed a commit that referenced this issue Dec 17, 2020
Signed-off-by: Alex Collins <alex_collins@intuit.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solution/workaround There's a workaround, might not be great, but exists type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants