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.

Sign up for GitHub

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

Jump to bottom

[backend] Updating KFP doesn't update existing scheduled runs #11296

Open
hbelmiro opened this issue Oct 14, 2024 · 3 comments · May be fixed by #11469
Open

[backend] Updating KFP doesn't update existing scheduled runs #11296

hbelmiro opened this issue Oct 14, 2024 · 3 comments · May be fixed by #11469
Assignees
@hbelmiro
Labels
area/backend kind/bug lifecycle/frozen

Comments

@hbelmiro
Copy link
Contributor

hbelmiro commented Oct 14, 2024 •
edited
Loading

When we upgrade KFP, the existing ScheduledWorkflow doesn't have spec.workflow.spec updated.
That leads to subsequent runs being executed with old images and possible missing parameters.

Workaround

Delete the scheduled run that is failing to execute, and then recreate it. Alternatively, you can duplicate the existing scheduled run.

Impacted by this bug? Give it a 👍.
@hbelmiro
Copy link
Contributor Author

/assign

@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Dec 14, 2024
@stale stale bot removed the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Dec 16, 2024
@hbelmiro
Copy link
Contributor Author

/lifecycle frozen

@hbelmiro hbelmiro linked a pull request Dec 16, 2024 that will close this issue
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hbelmiro hbelmiro

Labels
area/backend kind/bug lifecycle/frozen
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(backend): Synced ScheduledWorkflow CRs on apiserver startup hbelmiro/data-science-pipelines
1 participant
@hbelmiro