Backend MySQL error in submitting a new pipeline

[gioargyr]

Environment

• How did you deploy Kubeflow Pipelines (KFP)?
  I have a Kubeflow installation through Kubeflow manifests.
• KFP version:
  The version is 1.7.0
• KFP SDK version:
  1.8.19

Steps to reproduce

• I submitted a pipeline in my Kubeflow installation through a Notebook instance of elyra/kf-notebook:3.15.0

I got the error:

HTTP response body: {"error_message":"Error creating pipeline: Create pipeline failed: InternalServerError:
 Failed to add pipeline version to pipeline_versions table: Error 1364:
 Field 'PipelineSpec' doesn't have a default value

In my case the installation of Kubeflow was done by following your manifests's version 1.7.0
I found in namespace kubeflow, a pod mysql.
From inside the pod, I acted on database mlpipeline on table pipeline_versions:
First, I executed this command (mysql command line):
ALTER table pipeline_versions MODIFY PipelineSpec longtext NULL;

but, after that I got a new error for column PipelineSpecURI

HTTP response body: {"error_message":"Error creating pipeline: Create pipeline failed: InternalServerError: Failed to add pipeline version to pipeline_versions table: Error 1364: Field 'PipelineSpecURI' doesn't have a default value

I also executed the same command for column PipelineSpecURI:
ALTER table pipeline_versions MODIFY PipelineSpecURI longtext NULL;

After those 2 modification on table pipeline_versions on database mlpipeline, my pipelines now run successfully and I have no further issue.

There is already one relevant issue: #7568 , but in my opinion it is not properly resolved.

Do you have any comment for my case?

Impacted by this bug? Give it a 👍.

[chensun]

KFP 1.7.0 is very old. Can you check if this issue still exists on 2.0.3?

[github-actions]

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.

[rimolive]

Closing this issue as there is no activity. You can reopen it if issue persists.

[github-actions]

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.

[rimolive]

/close

[google-oss-prow]

@rimolive: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.