Initial update of empty postgres database does not work with 6.1.3
See original GitHub issueDescribe the bug Central postgres DB initialization does not work with 6.1.3
Version of dependency-check used The problem occurs using version 6.1.3 of the cli
Log file
Errors are Caused by: org.owasp.dependencycheck.data.nvdcve.DatabaseException: Database schema is out of date
and org.owasp.dependencycheck.data.nvdcve.DatabaseException: Database schema does not match this version of dependency-check
To Reproduce
For our central DB we are using a deployment of two instances of a postgres database in kubernetes. A init container downloads the core/src/main/resources/data/initialize_postgres.sql
from the tag corresponding to the dependency-check version of the container. After that the postgres DB is initialized with the downloaded file (there is no persistence, the DB is always empty at start). The initial update is done using a sidecar that uses the dependency-check docker container with the version corresponding to the tag.
The initialization works but the update fails with the given error messages.
Expected behavior Initialization and update of an empty postgres DB should work with 6.1.3
Additional context
I suspect that there are changes missing in the initialize_postgres.sql
file that are present in initialize.sql
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top GitHub Comments
If @jeremylong doesn’t beat me to it I will create and merge the fix for the ‘external’ database initialisation scripts tonight in order to ensure that the next release will function as expected.
Sorry about that - I forgot to update the external database scripts… They have been updated.