Rerunning InitialSetup for Organization Email and Initial Info

Summary

The user is facing issues after upgrading Airbyte to version 1.1 in a Kubernetes deployment on GCP. They encountered login issues due to NULL organization email in the database and are now getting errors when requesting user data. They are looking for a way to rerun the initialSetup or reseed necessary data.


Question

hey! is there any way to rerun the initialSetup where you provide your organization email and all the initial info?

I have a Kubernetes deployment in GCP(without abctl) and I just upgraded to the version 1.1(it was running a really old version before). When I set auth.enabled=true I couldn’t login to Airbyte, I was getting the Invalid username or password. error message(even though the password was correct).

I went into the DB and when I select * from public.organization; I noticed that my organization had a NULL value in the email column, I did a UPDATE on that record to set the organization email.

Now the password works, but I get another error message when my browser tries to request /api/v1/users/get route. I get the Failed to get user after login.

is my organization/user missing some important records or relations in other tables? is there a way I could rerun the initialSetup or reseed necessary data?



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

["rerun-initialsetup", "kubernetes-deployment", "gcp", "auth-enabled", "invalid-username-or-password", "organization-email", "api-route-error", "missing-records", "reseed-data"]

Is that email also set on the Default User entry in the user table?

And does the network tab give more details like the error message suggests?

yeah it is set, same email

I see this in the network tab, but IDK if it is really useful

I tried to create a local abctl setup and when I query the organization table I see my email correctly populated and I am able to log in

this makes me feel that my GCP setup is somehow broken with bad/missing data because we were running an older version and after all the upgrades that I did, it eiter did not run all the correct migrations or my organization is missing some crucial data that is created when you run the initial Quickstart setup to create the org.

I was hoping that it would be possible to fix the bad data somehow