Hi all, Hi all, I am new to Airbyte. I am working on deploying Airbyte via the official helm chart. I have decided to use PostgreSQL as an external database and configure the

values.yaml

as the document guide. The installation is almost perfect but I facing some issues with

temporal

as follows: here is the log from the deployment of the temporal • My environment: Postgres 13.7 Managed by Huawei RDS • Helm Chart latest version • Other values in

values.yaml

are set to default

Unable to create server. Error: could not build arguments for function "<http://go.uber.org/fx|go.uber.org/fx>".(*App).constructCustomLogger.func2 (/go/pkg/mod/go.uber.org/fx@v1.18.2/app.go:414): failed to build fxevent.Logger: could not build arguments for function "<http://go.temporal.io/server/temporal|go.temporal.io/server/temporal>".glob..func8 (/home/builder/temporal/temporal/fx.go:1025): failed to build log.Logger: received non-nil error from function "<http://go.temporal.io/server/temporal|go.temporal.io/server/temporal>".ServerOptionsProvider (/home/builder/temporal/temporal/fx.go:159): sql schema version compatibility check failed: version mismatch for keyspace/database: "temporal". Expected version: 1.9 cannot be greater than Actual version: 1.4.

sql schema version compatibility check failed: version mismatch for keyspace/database: "temporal". Expected version: 1.9 cannot be greater than Actual version: 1.4

It seems like you're encountering an issue with the schema version compatibility of your Temporal database. The error message indicates that the expected version of your Temporal database schema (1.9) is greater than the actual version (1.4). In a previous [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1678378615401469), a user encountered a similar issue after upgrading their helm chart version. It was suggested that the Temporal schema updates might not be automated and may need to be run manually. You might want to check the Temporal documentation for guidance on how to upgrade your Temporal schema: [Temporal Cluster Deployment Guide](https://docs.temporal.io/cluster-deployment-guide#postgresql). Also, another user asked if it's possible to drop the Temporal databases and let Airbyte recreate them by running the deployment. This could be another approach to consider, but please note that this might result in data loss if you have important data in your Temporal databases. If you continue to encounter issues, I would recommend reaching out to the Airbyte community on their [Slack channel](https://airbytehq.slack.com/archives/C021JANJ6TY/) or [forum](https://discuss.airbyte.io) for further assistance.

Not sure if related, but I ran into a similar error with the auto setup while pointing at an AWS RDS Postgres instance because of the TLS setup. Adding the following

extraEnv

vars helped get the automigrator up and running:

##  temporal.extraEnv [array] Additional env vars for temporal pod(s).
  ## Example:
  ##
  ## extraEnv:
  ## - name: SAMPLE_ENV_VAR
  ##   value: "key=sample-value"
  extraEnv:
    - name: SQL_TLS
      value: 'true'
    - name: SQL_TLS_DISABLE_HOST_VERIFICATION
      value: 'true'
    - name: SQL_TLS_ENABLED
      value: 'true'
    - name: SQL_HOST_VERIFICATION
      value: 'false'

Seems like it's worth trying since this issue mentions a temporal release that has almost nothing but TLS fixes in it 😬 Good luck!

Thank you. I have tried with your suggestion but it didn’t work for me.

Hi ! I don't know if you found the solution to your problem but I found a similar issue here https://github.com/airbytehq/airbyte/issues/20870 Deleting the TEMPORAL_VISIBILITY and TEMPORAL dbs worked for me (I was blocked with a similar issue on an upgrade to airbyte V0.50.30)