14110 2020-10-31 01:16:16 +0000 cve-check fails with 'attempt to write a readonly database' 2024-03-04 09:41:52 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 3.2 x86 Multiple RESOLVED FIXED Medium normal 5.0 1 kweihmann ross.burton meta.mr.watcher meta.watcher ralphs randy.macleod rybczynska --- --- Don't know oldest_to_newest 88531 0 kweihmann 2020-10-31 01:16:16 +0000 File: '/opt/build/poky/meta/classes/cve-check.bbclass', lineno: 241, function: check_cves 0237: else: 0238: vendor = "%" 0239: 0240: # Find all relevant CVE IDs. *** 0241: for cverow in conn.execute("SELECT DISTINCT ID FROM PRODUCTS WHERE PRODUCT IS ? AND VENDOR LIKE ?", (product, vendor)): 0242: cve = cverow[0] 0243: 0244: if cve in cve_whitelist: 0245: bb.note("%s-%s has been whitelisted for %s" % (product, pv, cve)) Exception: sqlite3.OperationalError: attempt to write a readonly database I suspect that, as the class is executed on multiple recipe workspaces at the same time, and sqlite is know to have issues with multiple clients executions (http://www.sqlite.org/faq.html#q5) we are running into the above problem. 88550 1 ross.burton 2020-11-05 07:41:29 +0000 Can you confirm what version of Poky you're using? 88569 2 kweihmann 2020-11-05 09:09:01 +0000 Bleeding edge master that was. To be exact revision 43e3a19c19e2d4f6b1d84c24413df6327540fab9 92785 3 ralphs 2022-03-16 19:02:53 +0000 I believe this is fixed by 440f07d211841147f2d2b6016a20b75747f45752 ("cve-check: get_cve_info should open the database read-only") 92820 4 ross.burton 2022-03-21 13:44:12 +0000 https://lists.openembedded.org/g/openembedded-core/message/162637 suggests that it may not have been sufficient. 95430 5 randy.macleod 2023-04-21 18:45:44 +0000 Moved en masse from 4.2 to 4.3 by Randy. 95495 6 rybczynska 2023-05-04 12:51:40 +0000 This should be fixed by OE-core 8efe99214d8b005f0ecac690ce5ba17b31758f92 ("cve-update-db-native: avoid incomplete updates"). Would be interested to know if it isn't the case. 98371 7 kweihmann 2024-03-02 09:05:42 +0000 Haven't had any issue in a long time now - I think this bug can be considered fixed 98373 8 ross.burton 2024-03-04 09:41:52 +0000 Agreed, thanks.