Fix migration to DB version 242 from gvmd 20.08 #1498
Merged
Conversation
This file contains 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
When running the migration to DB version 242, the vt_severities table only exists when migrating from a 21.04 development version, so the migration for that table must be skipped if it does not exist.
nichtsfrei
approved these changes
Apr 19, 2021
timopollmeier
added
the
backport-to-main
timopollmeier
added a commit
that referenced
this pull request
Apr 20, 2021
timopollmeier
added a commit
that referenced
this pull request
Apr 20, 2021
Fix migration to DB version 242 from gvmd 20.08 (backport #1498)
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:
Migration of the vt_severities is skipped if the table does not exist.
Why:
When running the migration to DB version 242, the vt_severities table
only exists when migrating from a 21.04 development version, so the
migration for that table must be skipped if it does not exist.
Closes #1497
How did you test it:
By creating a new database, running gvmd 20.08 to set it up and load the feed data, then migrating to 21.04.
Checklist: