W0911 03:12:55.601024 1 metadata_store_server_main.cc:550] Connection Aborted with error: ABORTED: In the given db, MLMDEnv table exists but no schema_version can be found. This may be due to concurrent connection to the empty database. Please retry connection. I0911 03:12:55.601061 1 metadata_store_server_main.cc:551] Retry attempt 4

[vak890]

Validation Checklist

• Is this a Kubeflow issue?
• Are you posting in the right repository ?
• Did you follow the Kubeflow installation guideline ?
• Is the issue report properly structured and detailed with version numbers?
• Is this for Kubeflow development ?
• Would you like to work on this issue?
• You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.

Version

1.9

Describe your issue

When I followed the kubeflow installation guide, metadata grpc deployment couldn't run successfully
kubectl logs -f metadata-grpc-deployment-786f94dc8b-kfrgc -n kubeflow
W0911 03:12:55.545574 1 metadata_store_server_main.cc:550] Connection Aborted with error: ABORTED: In the given db, MLMDEnv table exists but no schema_version can be found. This may be due to concurrent connection to the empty database. Please retry connection.
I0911 03:12:55.545694 1 metadata_store_server_main.cc:551] Retry attempt 0
W0911 03:12:55.559099 1 metadata_store_server_main.cc:550] Connection Aborted with error: ABORTED: In the given db, MLMDEnv table exists but no schema_version can be found. This may be due to concurrent connection to the empty database. Please retry connection.
I0911 03:12:55.559130 1 metadata_store_server_main.cc:551] Retry attempt 1
W0911 03:12:55.572381 1 metadata_store_server_main.cc:550] Connection Aborted with error: ABORTED: In the given db, MLMDEnv table exists but no schema_version can be found. This may be due to concurrent connection to the empty database. Please retry connection.
I0911 03:12:55.572420 1 metadata_store_server_main.cc:551] Retry attempt 2
W0911 03:12:55.586738 1 metadata_store_server_main.cc:550] Connection Aborted with error: ABORTED: In the given db, MLMDEnv table exists but no schema_version can be found. This may be due to concurrent connection to the empty database. Please retry connection.
I0911 03:12:55.586771 1 metadata_store_server_main.cc:551] Retry attempt 3
W0911 03:12:55.601024 1 metadata_store_server_main.cc:550] Connection Aborted with error: ABORTED: In the given db, MLMDEnv table exists but no schema_version can be found. This may be due to concurrent connection to the empty database. Please retry connection.
I0911 03:12:55.601061 1 metadata_store_server_main.cc:551] Retry attempt 4
F0911 03:12:55.614584 1 metadata_store_server_main.cc:555] Check failed: absl::OkStatus() == status (OK vs. ABORTED: In the given db, MLMDEnv table exists but no schema_version can be found. This may be due to concurrent connection to the empty database. Please retry connection.) MetadataStore cannot be created with the given connection config.
*** Check failure stack trace: ***

Steps to reproduce the issue

kustomize build apps/pipeline/upstream/env/cert-manager/platform-agnostic-multi-user | kubectl apply -f -

Put here any screenshots or videos (optional)

No response

[vak890]

I found that the schema_version field is present in MySQL

mysql log:

[juliusvonkohout]

It might be related to #2800 (comment) and the merged PRs, although I did not check the details.

[vak890]

@juliusvonkohout The solution is whether the kubeflow platform needs to be deployed in a new Kubernetes cluster, but our current Kubernetes cluster is native without any changes, and only some pods have been deployed in the cluster

[juliusvonkohout]

@juliusvonkohout The solution is whether the kubeflow platform needs to be deployed in a new Kubernetes cluster, but our current Kubernetes cluster is native without any changes, and only some pods have been deployed in the cluster

I do not understand your text. Please follow the new guidelines we just updated in the master branch in kubeflow/manifests/readme.md.

[juliusvonkohout]

/close

due to inactivity

[google-oss-prow]

@juliusvonkohout: Closing this issue.

In response to this:

/close

due to inactivity

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/test-infra repository.