Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Querying is failing on v1 site #1239

Closed
nichhk opened this issue Jun 9, 2022 · 1 comment
Closed

Querying is failing on v1 site #1239

nichhk opened this issue Jun 9, 2022 · 1 comment
Assignees
Labels
Role: Backend Related to API or other server-side work Role: DevOps infrastructure, CI or related work Size: 8pt Can be done in 31-48 hours

Comments

@nichhk
Copy link
Member

nichhk commented Jun 9, 2022

The v1 code was previously deployed from release/v1.5.0 branch. When I was working on updating the v1 site to make the "Contact Us" functionality work, I made my fixes on dev and pushed a new API image from dev. From release/v1.5.0 to dev, the API code changed enough to make queries to the existing prod database fail. Specifically, the error is: UndefinedColumnError: column request_types.agency_id does not exist (Sentry).

Ideally, we would be able to run "alembic,upgrade,head" using this config (modified to target the prod DB) with this command: aws ecs run-task --cli-input-json file://alembic_task.json; in order to bring the DB up-to-date with the changes in the API code. However, the alembic upgrade scripts were changed after they were already applied on the prod database. Alembic doesn't know to reapply upgrades that have changed, and the following upgrades relied on the previous upgrades having that change, so the upgrades failed.

I think the only option is to drop the database, recreate it, and then run "alembic,upgrade,head". I will need access to an SSH key from a former team member in order to do this since the DB is not publicly accessible.

@nichhk nichhk self-assigned this Jun 9, 2022
@nichhk nichhk added this to the v2.1 Launch milestone Jul 19, 2022
@nichhk nichhk added Role: Backend Related to API or other server-side work Size: 8pt Can be done in 31-48 hours Role: DevOps infrastructure, CI or related work labels Jul 19, 2022
@nichhk
Copy link
Member Author

nichhk commented Nov 17, 2022

This is obsolete since we are focusing on v2 now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Role: Backend Related to API or other server-side work Role: DevOps infrastructure, CI or related work Size: 8pt Can be done in 31-48 hours
Projects
Status: Done (without merge)
Development

No branches or pull requests

1 participant