Closed SaberStrat closed 1 month ago
Confirmed, will push out a fix ASAP.
This only affects the old BOM processing task though. You can enable the new one in the settings (Experimental -> BOM Processing V2), or alternatively roll back to 4.11.1 in the meantime.
v4.11.3 is out, apologies for the inconvenience.
https://github.com/DependencyTrack/dependency-track/releases/tag/4.11.3
Thank you for the lightning fast reaction!
I rolled back to .1. Didn't want to switch to BOM Processing v2 because of its experimental nature yet. Oh well ;)
I'll try .3 later today.
Looking good, no error upon upload anymore.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Current Behavior
When successfully (no HTTP error) uploading a BOM of a new project version, created by the Gradle plugin org.cyclonedx.bom version 1.6.1, the apiserver container logs throw this
In the Dependency-Track UI, the project version is shown as unprocessed (empty fields "Last BOM Import", "BOM Format", and no vulnerabilities).
Restarting the apiserver does not help this from happening on new uploads.
Workaround: trigger a Reanalyze manually.
Steps to Reproduce
Expected Behavior
No Errors upon upload of the BOM
Dependency-Track Version
4.11.2
Dependency-Track Distribution
Container Image
Database Server
PostgreSQL
Database Server Version
13.2.0
Browser
Google Chrome
Checklist