Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

database is locked errors with SQLite #678

Open
2 tasks done
akijakya opened this issue May 7, 2024 · 2 comments
Open
2 tasks done

database is locked errors with SQLite #678

akijakya opened this issue May 7, 2024 · 2 comments

Comments

@akijakya
Copy link
Contributor

akijakya commented May 7, 2024

Description

During the implementation of Azure e2e tests with SQLite as database, the full scan test was constantly failing due to a database is locked error, mainly at the waiting until asset is found in riskiest assets dashboard and waiting until findings trends dashboard is populated with vulnerabilities steps.

Example:
failed to get dashboard riskiest assets: status code=500: failed to get riskiest assets for vulnerabilities: failed to get riskiest assets: failed to get assets: failed to get assets. status code=500: failed to get assets from db: failed to query DB: database is locked

These errors were not present when testing with other cloud providers.

Checklist

Copy link

github-actions bot commented Jul 7, 2024

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 14 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.

@github-actions github-actions bot added the stale label Jul 7, 2024
Copy link

This issue has been marked stale for 14 days, and is now closed due to inactivity. If the issue is still relevant, please re-open this issue or file a new one. Thank you!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 21, 2024
@paralta paralta reopened this Jul 22, 2024
@paralta paralta removed the stale label Jul 22, 2024
@ramizpolic ramizpolic transferred this issue from openclarity/vmclarity Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants