THREESCALE-12013 - after upgrading to 2.16 system-app has still old db schema#1125
Merged
tkan145 merged 2 commits into3scale:masterfrom Nov 20, 2025
Merged
THREESCALE-12013 - after upgrading to 2.16 system-app has still old db schema#1125tkan145 merged 2 commits into3scale:masterfrom
tkan145 merged 2 commits into3scale:masterfrom
Conversation
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
eguzki
approved these changes
Nov 20, 2025
eguzki
approved these changes
Nov 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fix THREESCALE-12013
We rely heavily on the Deployment revision to trigger the migration, however during an upgrade the revision will not change until the operator updates the Deployment with the new image first, then causes the migration to run after the Deployment has been deployed.
Verification steps
system-app-prejob fired before the new system-app is deployed and then thesystem-app-postjob