[yocto-security] CVE-Tool build issues in Open BMC project

Ross Burton ross.burton at intel.com
Mon Aug 5 07:38:17 PDT 2019


On 31/07/2019 22:03, Chittari Pabba wrote:
> Hello All:
> 
> We are trying to enable cve-check tool in our Open BMC project build, 
> but we could not able to succeed, build is troughing below errors. 
> Anyone noticed similar issues enabling of cve-check tool open BMC build? 
> Any help highly appreciates.
> 
> Initialising tasks: 100% 
> |####################################################################################################################################################################################################| 
> Time: 0:00:04
> 
> Sstate summary: Wanted 5 Found 0 Missed 5 Current 1625 (0% match, 99% 
> complete)
> 
> NOTE: Executing SetScene Tasks
> 
> NOTE: Executing RunQueue Tasks
> 
> ERROR: cve-update-db-1.0-r0 do_populate_cve_db: Error executing a python 
> function in exec_python_func() autogenerated:
> 
> The stack trace of python calls that resulted in this exception/failure was:
> 
> File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
> 
>       0001:
> 
> *** 0002:do_populate_cve_db(d)
> 
>       0003:
> 
> File: 
> '/home/chittari/Projects/git-clones/openbmc/meta/recipes-core/meta/cve-update-db.bb', 
> lineno: 31, function: do_populate_cve_db
> 
>       0027:    JSON_TMPFILE = d.getVar("CVE_CHECK_DB_DIR") + '/nvd.json.gz'
> 
>       0028:
> 
>       0029:    # Connect to database
> 
>      0030:    db_file = d.getVar("CVE_CHECK_DB_FILE")
> 
> *** 0031:    conn = sqlite3.connect(db_file)
> 
>       0032:    c = conn.cursor()
> 
>       0033:
> 
>       0034:    initialize_db(c)
> 
>       0035:
> 
> Exception: sqlite3.OperationalError: unable to open database file

That's not a very useful error from sqlite is it.  I'd see if the file 
exists (maybe the permissions are wrong?) or try opening it in the 
sqlite command line tool to see if it is corrupted.

I'm assuming you're using oe-core master here, if openbmc is backporting 
the changes then there's a chance some commits are missing.

Ross


More information about the yocto-security mailing list