-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[backend] Cannot create new pipeline or upload new version to existing pipelines #7568
Comments
The issue is solved with a workaround. First Then change the column of Description in Table pipeline_versions to accept NULL values
Problem solved. Still don't know why issue happened why it's working for quite some time. I suspect there are some mismatch between frontend and backend codes, which makes the description value does not get passed correctly from UI to db |
Maybe you could check your mysql config and see if there's any recent change? In kfp the description should be optional. |
Hello, I am reopening this issue as I had a similar one.
In my case the installation of Kubeflow was done by following your but, after I got a new error for column
I also executed the same command for column After those 2 modification on table Do you have any comments on this? |
Environment
Steps to reproduce
Previously, everything looks fine. But all of a sudden, couldn't upload pipelines or create pipelines either from UI or from cli. The error messages are like follows:
Upload version to existing pipeliens:
Create new pipelines:
E0415 03:30:50.340822 7 pipeline_upload_server.go:240] Failed to upload pipelines. Error: Error creating pipeline: Create pipeline failed: InternalServerError: Failed to add pipeline version to pipeline_versions table: Error 1364: Field 'Description' doesn't have a default value: Error 1364: Field 'Description' doesn't have a default value
No matter which yaml I use, the one generated by kfp cli, or the one in sample code, all get same errors. It looks like a global issue instead of the format in one single yaml file. No clue at why it happened...thanks for checking...
The text was updated successfully, but these errors were encountered: