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

Fix db-init Flyway migration issues #3521

Closed
brostk opened this issue Sep 26, 2024 · 0 comments
Closed

Fix db-init Flyway migration issues #3521

brostk opened this issue Sep 26, 2024 · 0 comments
Assignees
Labels
RC VRO root cause VRO VRO-team

Comments

@brostk
Copy link
Contributor

brostk commented Sep 26, 2024

User Story

As an engineer, I want db-init to run again, so that database migrations can occur.

Acceptance Criteria

[ ] db-init job in ArgoCD executes successfully

Not included in this work

A future ticket will be created to address db-init's place as an application versus being a job which is executed alongside relevant applications' deployments. This ticket is only intended to fix the current flyway migration issues preventing the job from executing successfully.

Notes about work

  • Flyway migration to version 1.7 seems to have been executed and then reverted, as a simultaneous change was made in version 2.0. This is resulting in a failed migration, with the exception reading "Detected applied migration not resolved locally: 1.7"
  • There is a PR up currently which sets the flag "flyway.ignoreMissingMigrations=true", which may resolve the issue.
  • Running a repair job with flyway may also resolve the issue if the above flag does not, which can be added before the migrate call in our startup scripts for the app.
@meganhicks meganhicks added the RC VRO root cause VRO label Sep 26, 2024
brostk added a commit that referenced this issue Sep 30, 2024
## What was the problem?
flyway repair needs to be run to resolve 1.7 migration issues.

Associated tickets or Slack threads:
- #3521



[^1]: [Pull-Requests
guidelines](https://github.com/department-of-veterans-affairs/abd-vro/wiki/Pull-Requests).
If PR is significant, update [Current Software
State](https://github.com/department-of-veterans-affairs/abd-vro/wiki/Current-Software-State)
wiki page.
[^secrel]: To check if a PR will succeed in the SecRel workflow, [test
PRs in the SecRel
pipeline](https://github.com/department-of-veterans-affairs/abd-vro-internal/wiki/Secure-Release-process#to-test-prs-in-the-secrel-pipeline).
@brostk brostk closed this as completed Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RC VRO root cause VRO VRO-team
Projects
None yet
Development

No branches or pull requests

2 participants