Error upgrading Airbyte version due to 'column actor.default_version_id does not exist'

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

When trying to upgrade Airbyte to the latest version, an error ‘column actor.default_version_id does not exist’ occurred. User is seeking help to resolve this issue.


Question

Hey folks :meow_fingerguns:, we were trying to upgrade Airbyte today to the latest version from 0.50.55. However, the upgrade failed due to an error message column actor.default_version_id does not exist. Has anyone encountered this or resolved it? We are still encountering it after downgrading back to our previous version


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["upgrade", "airbyte", "error-message", "column-actor.default_version_id"]
2

you might try to run

3

kubectl logs -n airbyte-abctl airbyte-abctl-airbyte-bootloader --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig

4

Anything in particular that I should see in the logs? The only thing I really notice is that it mentions that the version of the table schema it is using for 0.50.55 is older than the one that is in place. I’m guessing there’s been a migration at some point but I haven’t seen how to roll back migrations in Airbyte. We’ve got a snapshot so we’ll try to restore to that and see if that resolves the issue

5

I have done the same :smile: then created a replica to play with the new version of airbyte

6

Cool. Did you ever encounter this issue? This is just our Beta environment so it’s not too bad but the upgrade instructions don’t seem to have mentioned it. I’ll maybe try creeping up the upgrades rather than a big jump

7

I think I migrated from the similar version

8

I’ve solved this issues by doing some shitty alter tables and updates manually, btw, I don’t recommend this since you can make a really mess. Then I’ve tried to migrate everything to the closer version that I had and then so on.

9

there were some data types in the DB that needed changing so I changed them from the main admin account manually

10

usually in the logs they say what fails

11

but now encountering the new errors and cannot find any help :smile:

12

Jeez. Thanks both, I was tempted by altering the table to add the column but will maybe slowly apply the updates. It’ll give me a chance to catch up on some reading while it deploys :slightly_smiling_face: