Hello folks, I have just updated my Airbyte instan...
# replication-ask-ai
s
Hello folks, I have just updated my Airbyte instance from 0.40.23 to v0.50.5 with process from docs. (https://docs.airbyte.com/operator-guides/upgrading-airbyte#upgrading-on-docker)
docker compose down
git pull
./run-ab-platform.sh -r
./run-ab-platform.sh -b
Now I get the error message service: "bootloader" didn't complete successfully: exit 255 The logs are indicating, that the table
public.actor_definition_version
does not exist. Are there any hard stops I need to respect when updating?
plus1 2
k
Based on the information provided in the extracts, it seems like you've followed the correct steps for upgrading Airbyte on Docker as outlined in the [official documentation](https://docs.airbyte.com/operator-guides/upgrading-airbyte#upgrading-on-docker). However, the error message you're encountering suggests that there might be an issue with the database migration during the upgrade process. The
public.actor_definition_version
table might be a new addition in the newer versions of Airbyte and it seems like it's not being created during the upgrade process. Unfortunately, the extracts do not provide specific information on how to resolve this issue. It might be related to a bug or an issue with the specific versions you're upgrading from and to. 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. They might be able to provide more specific guidance or troubleshooting steps.
s
Full logs:
m
@Benoit Moriceau (Airbyte) as you said yesterday about jumping from a old version to more recent ones. Do we have any guidelines about this topic?
b
As far as I know, there is no guideline. It looks that a DB migration didn't happened here.
s
Is there any way to trigger the migrations manually?
l
@Simon did you figure out a solution or workaround for this, I am having the same issue upgrading to v0.50.19 - I also tried v0.50.0 and v0.50.5
s
Unfortunately not, i had to completely reinstall our instance.