Bug: Neo.ClientError.Statement.EntityNotFound when ingesting data

[Daniel-CS-Team]

Description:

Sometimes, when ingesting data into Bloodhound, I receive the error Neo.ClientError.Statement.EntityNotFound. The entire ingest is then failed and no data is ingested.

Are you intending to fix this bug?

no

Component(s) Affected:

• API
• Neo4j

Steps to Reproduce:

Not simply reproducible, but consistent with same database and ingest file.

Expected Behavior:

If a Neo.ClientError is encountered, produce an actionable error message, ignore the specific node or edge and continue the ingest.

Actual Behavior:

Generic error is shown, without any helpful debug information and ingest is failed.
The given node id really does not exist, therefor it is not possible to get any further information...

Screenshots/Code Snippets/Sample Files:

Neo4jError: Neo.ClientError.Statement.EntityNotFound (Unable to load NODE with id 3453934.)
cannot use this transaction, because it has been committed or rolled back either because of an error or explicit termination
update nodes by error on statement (unwind $p as p merge (n:AZBase {objectid:p.objectid}) set n += p, n:AZBase, n:AZDevice;): cannot use this transaction, because it has been committed or rolled back either because of an error or explicit termination

Environment Information:

BloodHound: 8.6.1

Collector: Independent of Collector, happens with Azurehound but also with manual created JSON

OS: Bloodhound docker image

Go (if API related): Bloodhound docker image

Database (if persistence related): neo4j 4.4.48

Docker (if using Docker): AWS ECS

Additional Information:

Potential Solution (optional):

Related Issues:

Contributor Checklist:

• I have searched the issue tracker to ensure this bug hasn't been reported before or is not already being addressed.
• I have included relevant environment information details.
• I have checked that any JSON files I am attempting to upload to BloodHound are valid.

[github-actions]

This issue has been automatically marked as stale because it has not had activity for 90 days. It will be closed in 90 days if there is no further activity.