Fix sqlite3.OperationalError: no such table: VULNERABILITIES error #1067
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
BraulioV
suggested changes
Feb 16, 2021
Co-authored-by: Braulio Vargas López <[email protected]>
BraulioV
approved these changes
Feb 16, 2021
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.
Hi,
This PR fixes the following error:
produced when launching a scan test on a clean installation of wazuh (by default cve.db does not exist until vuln detector is activated and wazuh-modulesd is restarted).
The fix has consisted of adding a new fixture that after applying the
ossec.confconfiguration and restartingwazuh-modulesdthere is a wait (up to a maximum of 30 seconds) until the database and tables have been created.This is done before doing any operation with the database (insert vulnerabilities ...)
Tests
pycodestyle --max-line-length=120 --show-source --show-pep8 file.pyRegards.