Open ccfahe opened 2 months ago
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.
See #3815, our dtrack did this when the bom version where not supported by dependency track (CycloneDx 1.5)
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