-
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
Cron Workflows UI Fails to Load #14009
Comments
can u try with #13856 |
That seems like all the workflows won't render at all |
But if I were to try this, is there a pre-built image or would I have to build it myself? |
build yourself |
We ended up updating the CRDs on the cluster (previously had only updated the image tags) and deleting a few old cron workflows and suddenly the UI started working again. |
It seems to be related to the fact that schedule was abandoned in 3.6 and replaced by schedules. https://argo-workflows.readthedocs.io/en/latest/deprecations/#cronworkflow-schedule |
'schedule' still works in 3.6, but is marked deprecated. Both 'schedule' and 'schedules' work. |
@shuangkun is correct, the UI code only handles schedules, not schedule |
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?
What Happened?
When we upgraded from argo workflows 3.5.5 to argo 3.6.2, the Cron Workflows tab errors with a "e.spec.schedules is undefined" error (see screenshot below). This only happens in namespaces that had cron workflows created before the upgrade. If a namespace did not have any previous cron workflows, then creating a new workflow works and is properly displayed.
I should say that it seems like the workflow does not display correctly in the UI. It still exists and runs as scheduled.
What did I expect to happen?
I would think that the UI would work with the old workflows and that I wouldn't have to re-create all our previous cron workflows in order to see them in the UI.
Version(s)
3.6.2
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.
This is a workflow server issue. I assume creating any workflow with a schedule on 3.5.* and then upgrading to 3.6.2 would have this problem
Logs from the workflow controller
The text was updated successfully, but these errors were encountered: