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

Problem when trying to add an external reference to a Threat Report #510

Closed
AZobec opened this issue Feb 19, 2020 · 1 comment
Closed

Problem when trying to add an external reference to a Threat Report #510

AZobec opened this issue Feb 19, 2020 · 1 comment
Assignees
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

@AZobec
Copy link

AZobec commented Feb 19, 2020

Description

I created a new Threat report.
I created a new external reference.
I wanted to add this new reference to the new report previously created.

And I got an error from grakn :

opencti_1 | error: [GRAKN] executeWrite error > Cannot read property 'map' of null {"stack":"TypeError: Cannot read property 'map' of null\n at /opt/opencti/build/index.js:1:28310\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (internal/process/task_queues.js:93:5)\n at async W (/opt/opencti/build/index.js:1:5188)\n at async xe (/opt/opencti/build/index.js:1:27869)\n at async Me (/opt/opencti/build/index.js:1:30421)"} opencti_1 | error: [OPENCTI] Technical error > Cannot read property 'map' of null {"locations":[{"line":6,"column":5}],"path":["externalReferenceEdit","relationAdd"],"extensions":{"code":"INTERNAL_SERVER_ERROR","exception":{"stacktrace":["TypeError: Cannot read property 'map' of null"," at /opt/opencti/build/index.js:1:28310"," at runMicrotasks (<anonymous>)"," at processTicksAndRejections (internal/process/task_queues.js:93:5)"," at async W (/opt/opencti/build/index.js:1:5188)"," at async xe (/opt/opencti/build/index.js:1:27869)"," at async Me (/opt/opencti/build/index.js:1:30421)"]}}}

I tested to add external references to old Threat Reports, I had the same issue.

Environment

  1. OS (where OpenCTI server runs): { Debian 10.2 }
  2. OpenCTI version: { OpenCTI 3.0.0 }
  3. OpenCTI client: { frontend }
  4. Other environment details: Using docker with latest images

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. going on http://opencti.local.cert.opmd.fr/dashboard/reports/all and then click "+" to create a new report
  2. Create a new external reference while on the report page (with "+" button)
  3. Error : "Une erreur est survenue, merci de réessayer plus tard"
  4. Grakn Error : opencti_1 | error: [GRAKN] executeWrite error > Cannot read property 'map' of null {"stack":"TypeError: Cannot read property 'map' of null\n at /opt/opencti/build/index.js:1:28310\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (internal/process/task_queues.js:93:5)\n at async W (/opt/opencti/build/index.js:1:5188)\n at async xe (/opt/opencti/build/index.js:1:27869)\n at async Me (/opt/opencti/build/index.js:1:30421)"} opencti_1 | error: [OPENCTI] Technical error > Cannot read property 'map' of null {"locations":[{"line":6,"column":5}],"path":["externalReferenceEdit","relationAdd"],"extensions":{"code":"INTERNAL_SERVER_ERROR","exception":{"stacktrace":["TypeError: Cannot read property 'map' of null"," at /opt/opencti/build/index.js:1:28310"," at runMicrotasks (<anonymous>)"," at processTicksAndRejections (internal/process/task_queues.js:93:5)"," at async W (/opt/opencti/build/index.js:1:5188)"," at async xe (/opt/opencti/build/index.js:1:27869)"," at async Me (/opt/opencti/build/index.js:1:30421)"]}}}

Expected Output

I expected to link the external references I created to my Threat Report.

Actual Output

Nothing - just the error message

Additional information

@SamuelHassine SamuelHassine self-assigned this Feb 19, 2020
@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label Feb 19, 2020
@SamuelHassine SamuelHassine added this to the Release 3.0.0 milestone Feb 19, 2020
@SamuelHassine SamuelHassine reopened this Feb 19, 2020
@SamuelHassine
Copy link
Member

Hotfixed in the new image of the 3.0.0. If you are using Docker, please re-pull the images, if you are using manual deployment, please use the new packages.

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 19, 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

2 participants