`Cannot return null for non-nullable field` error in various areas of OpenCTI
Description
Three areas seeing the same Cannot return null for non-nullable field error:
- 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. - CSV Mapper: import failing due to 'Cannot return null for non-nullable field' error.
- 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
- OS (where OpenCTI server runs): docker
- OpenCTI version: 5.12.31
- OpenCTI client: frontend/python
- Other environment details:
Reproducible Steps
UI:
- Navigating to the page such as "Arsenal" page
- Unsure what's causing this
CSV Mapper:
- Create a CSV Mapper configuration that contains a Country or Sector.
- Upload and import CSV file using the mapper configuration created.
- Errors is displayed when hovering over the failed import task.
Connector: None
Expected Output
Actual Output
Additional information
Screenshots (optional)
have you reproduced it @jborozco ?
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.
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