Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merging entities : recurring bug #710

Closed
Fred-certeu opened this issue May 20, 2020 · 1 comment
Closed

Merging entities : recurring bug #710

Fred-certeu opened this issue May 20, 2020 · 1 comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Fred-certeu
Copy link

Fred-certeu commented May 20, 2020

Please replace every line in curly brackets { like this } with an appropriate answer, and remove this line.

Description

In some cases when trying to merge two entities, the following error is returned:
"There is more than one thing of type [stix_relation_embedded] that owns the key [xxxxxx] of type [internal_id_key]

image

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: 3.2.2
  3. OpenCTI client: { e.g. frontend or python }
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. { e.g. Run ... }
  2. { e.g. Click ... }
  3. { e.g. Error ... }

Expected Output

Merging 2 entities

Actual Output

Merging is not done. Error message (see above)

Additional information

I seems that the bug comes when the two entities to merge share some relationships with other entities (e.g. 2 malware having "indicate" relationships with the same indicators)

@cvdsouza
Copy link

+1 on this bug. We have seen it in our instance as well.

@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label May 22, 2020
@SamuelHassine SamuelHassine added this to the Release 3.3.0 milestone May 22, 2020
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

3 participants