dependency-track icon indicating copy to clipboard operation
dependency-track copied to clipboard

Bom.xml showing zero components after upload (Version server V4.6.3)

Open ccfahe opened this issue 1 year ago • 2 comments

Current Behavior

I have my deptrack server running on open shift with API , Frontend and PostgreSql containers. When I tried to upload bom.xml it showed zero components processed in spite of bom.xml having components.

Same bom.xml I tried with my local deptrack server and I can see all components.

The difference is in local I am using dep track container image to run server and in Openshift to run container along with potsgreSql

Steps to Reproduce

1.I have my deptrack server running on open shift with API , Frontend and PostgreSql containers. When I tried to upload bom.xml it showed zero components processed in spite of bom.xml having components.

Same bom.xml I tried with my local deptrack server and I can see all components.

The difference is in local I am using dep track container image to run server and in Openshift to run container along with potsgreSql

Expected Behavior

It should show components

Dependency-Track Version

4.7.x

Dependency-Track Distribution

Container Image

Database Server

PostgreSQL

Database Server Version

No response

Browser

Google Chrome

Checklist

ccfahe avatar May 19 '24 06:05 ccfahe

Please consult the logs of your API server container running in OpenShift. If the BOM fails to be processed, you'll see error logs there.

On a side note, 4.6.3 is now almost two years old. The current version is 4.11. If your issue is caused by a bug it is very likely that it is already fixed in a newer version. Please consider upgrading.

nscuro avatar May 19 '24 10:05 nscuro

See #3815, our dtrack did this when the bom version where not supported by dependency track (CycloneDx 1.5)

Maxouwell avatar Jun 06 '24 09:06 Maxouwell

Newer versions of DT also include schema validation, which should make issues like this a lot more obvious to users and API clients. Closing this as no further details were provided and the solution is likely to just upgrade to a newer version.

nscuro avatar Sep 16 '24 20:09 nscuro

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.

github-actions[bot] avatar Oct 18 '24 10:10 github-actions[bot]