Track when vuln ingestion fails to set finding ids
What does this MR do and why?
While rolling out CVS, we noticed that some batches failed the security ingestion process
when the finding_id
attribute was nil
in the finding map. Upon further investigation,
it became apparent that finding maps with duplicate UUID values would be deduplicated
by the base insertable task, and thus would in rare instances cause the returned data
size to mismatch the input finding maps, ultimately causing the finding_id
to remain
nil
for some of the maps.
Relates to GlobalAdvisoryScanWorker: null value in vulnera... (#432870 - closed) • Oscar Tovar • 16.7
Screenshots or screen recordings
N/A
How to set up and validate locally
The best way to reproduce this consistently is by running the spec added where all finding maps have the same UUID.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.