opencti icon indicating copy to clipboard operation
opencti copied to clipboard

`Cannot return null for non-nullable field` error in various areas of OpenCTI

Open brianyschae opened this issue 1 year ago • 3 comments

Description

Three areas seeing the same Cannot return null for non-nullable field error:

  1. UI: When navigating the OpenCTI platform which includes but not limited to the pages: "Arsenal" and "Cases", we encounter an error Cannot return null for non-nullable field.
  2. CSV Mapper: import failing due to 'Cannot return null for non-nullable field' error.
  3. Connector: This also has been an error that occurs in the in-house built "External Import" connectors, when attempting to ingest data. The error log is: Cannot return null for non-nullable field Country.objectMarking

Environment

  1. OS (where OpenCTI server runs): docker
  2. OpenCTI version: 5.12.31
  3. OpenCTI client: frontend/python
  4. Other environment details:

Reproducible Steps

UI:

  1. Navigating to the page such as "Arsenal" page
  2. Unsure what's causing this

CSV Mapper:

  1. Create a CSV Mapper configuration that contains a Country or Sector.
  2. Upload and import CSV file using the mapper configuration created.
  3. Errors is displayed when hovering over the failed import task.

Connector: None

Expected Output

Actual Output

Additional information

Screenshots (optional)

image image

brianyschae avatar Feb 14 '24 18:02 brianyschae

have you reproduced it @jborozco ?

Jipegien avatar Feb 16 '24 10:02 Jipegien

no sorry, I think I meant to validate another issue I was treating. I actually don't manage to reproduce this bug on the demo environment.

jborozco avatar Feb 16 '24 10:02 jborozco

Hello,

For old platforms and before model enforcement, we have a few customers and instances facing those kinds of issue. This is unfortunately not a bug but a database consistency issue. We have internal procedures for this.

Please reach me directly on Slack and we will be able to help you. Another radical solution could be to reset your platform completely which is not whished is most cases.

We have taken measures since several versions to enforce schema and robustness of the platform and doing this also highlight problems that were ignored in past versions.

Kind regards, Samuel

SamuelHassine avatar Feb 16 '24 23:02 SamuelHassine