I ve been running 0 40 32 in production for a few months and Airbyte #replication-ask-ai

I've been running 0.40.32 in production for a few ...

jonty

07/10/2023, 11:27 AM

I've been running 0.40.32 in production for a few months, and wanted to upgrade to the latest version (0.50.7). I followed the instructions at https://docs.airbyte.com/operator-guides/upgrading-airbyte/. However, I'm getting the following error when trying to bring the docker containers back up (using either

./run-ab-platform.sh -b

or `docker compose up -d`:

Copy code

service "bootloader" didn't completed successfully: exit 255

Running the following command:

docker compose logs -f bootloader

gives this output.

Copy code

airbyte-bootloader  | 2023-07-10 11:21:07 ERROR i.a.b.Application(main):25 - Unable to bootstrap Airbyte environment.
airbyte-bootloader  | org.jooq.exception.DataAccessException: SQL [select distinct "public"."actor_definition"."id", "public"."actor_definition_version"."docker_repository", "public"."actor_definition"."actor_type", "public"."actor_definition_version"."protocol_version" from "public"."actor_definition" join "public"."actor" on "public"."actor"."actor_definition_id" = "public"."actor_definition"."id" join "public"."actor_definition_version" on "public"."actor_definition_version"."id" = "public"."actor_definition"."default_version_id"]; ERROR: relation "public.actor_definition_version" does not exist

So, it looks like the DB schema is invalid. Is there something that I missed in the upgrade? Any ideas on how to rectify this?

kapa.ai

07/10/2023, 11:27 AM

A message from kapa.ai

kapa.ai

07/10/2023, 11:28 AM

Based on the error message you're seeing, it seems like there might be an issue with the database schema during the upgrade process. This could be due to a direct upgrade from an older version to a much newer one, which might not be supported due to breaking changes introduced in certain versions. If your current version of Airbyte is less than v0.32.0-alpha-patch-1, you first need to upgrade to this version before upgrading to any later version. This is because there are breaking changes made in v0.32.0-alpha-patch-1, and the logic for these changes is removed in later versions, making it impossible to upgrade directly [source](https://docs.airbyte.com/operator-guides/upgrading-airbyte). Here are the steps to upgrade to v0.32.0-alpha-patch-1: 1. If you are in a cloned Airbyte repo, v0.32.0-alpha-patch-1 can be pulled from GitHub with

Copy code

git checkout v0.32.0-alpha-patch-1

2. If you are running Airbyte from downloaded

docker-compose.yaml

and

.env

files without a GitHub repo, run

wget -N <https://raw.githubusercontent.com/airbytehq/airbyte/v0.32.0-alpha-patch-1/{.env,flags.yml,docker-compose.yaml}>

to pull this version and overwrite both files. After upgrading to v0.32.0-alpha-patch-1, you can then proceed to upgrade to the latest version following the standard upgrade process. If you've already followed these steps and are still encountering issues, it might be helpful to check the ownership of your external RDS tables for Airbyte. One user reported a similar issue and managed to fix it by transferring the ownership of the tables to the Airbyte user [source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1668783794472369). If none of these solutions work, it would be best to reach out to the Airbyte community on their [Slack channel](https://airbytehq.slack.com) or [forum](https://discuss.airbyte.io) for further assistance.

jonty

07/10/2023, 12:41 PM

OK, so I changed the

.env

version to

0.50.0

and that works, thankfully 😟

8 Views

Open in Slack

Previous Next