-
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
3.5: Cannot list archived workflow in UI with /archived-workflows/
#13356
Comments
other question is, user curl cmd to get wf, can reponse successfully, but list wf with limit, hangs
|
https://terrytangyuan.github.io/2023/08/14/argo-workflows-v3.5/ I know it use the "Unified workflows list UI and API",but the list cmd with curl no any responses and hangs. |
/archived-workflows/
Duplicate of #12545, #13126 (reply in thread), etc.
Correct, there is no split UI in 3.5+, as the blog post says. They are combined. The archived workflows API still exists, but the workflows API will now return archived workflows as well and the UI pages are combined.
This is unrelated. Please keep issues on a single topic. You also used a screenshot despite me asking you not to several times before as they are not accessible. As a result I had to stare at your screenshot and manually type your API query. Again, please do not use screenshots of code or logs or config. Use text. Your API query in the screenshot is:
The That invalid query parameter may mean that you're making a request with no limit, hence it will take very long. You can look at your Server logs. Additionally, your bearer token is also visible in the screenshot. You'll want to rotate your Secret. |
it's correct, you can take a look at debug informations.
thanks for your reminder, dose no matter, it's only test env
we make the image from source code, can the push the image to our internal image repo |
I think you misunderstood me. In this case, by image I meant your screenshot (PNG). I have edited my comment to clarify that.
That too would be easier in text form than with a screenshot that I have to zoom into. If it's correct, I can't reproduce this hanging and neither can our tests. I would drill that down to a minimal reproduction and if it still seems like a bug to you, you can open a separate bug report with that reproduction. And as I wrote before, you'd want to check the Server logs. There are some remaining performance issues in 3.5 like #13295 but I haven't seen any reports of hanging indefinitely. In those cases, which particularly impact larger workflows, it may take 10+ seconds, but it still returns eventually. Again the Server logs will reveal information, as will your DB logs etc. |
@agilgur5 Could you give me a exmaples for the curl request?
like this? |
I usually follow the Access Token docs.
An
Again, I'd use the Note that the UI uses the API, as does the CLI (when in Server mode) |
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
expect to list archived workflow like version 3.4.9:
but under version v3.5.8, can not list archived workflow:
Version(s)
v3.5.8
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
only create a normal wf, and waiting the wf was archived.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: