Check DB versions before CERT severity updates #1376
Merged
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:
When rebuilding the SCAP or CERT database, check if the other one
has the correct version. If not, skip updating the CERT severity
scores.
Why:
This fixes an issue where the SCAP DB update during migration
does not work because the CERT DB is not migrated yet and therefore
incompatible.
How did you test it:
This was tested by running
gvmd --migrate
after the following:After each step, the database was fully synced/rebuilt by letting gvmd run
normally until the regular update finished.
After setting a high version number, it was also set to 1 after the test run
and migrated.
Checklist: