Bug on validating changed date time range of parent device

Summary

We currently have a bug on the backend, when we try to patch a device mount action that has an open end to have a fixed end date in a situation that we have a child device mount that already has an end date.

Steps to reproduce

1. Create device 1
2. Create device 2
3. Create a test configuration
4. Mount device 1 from 2024-01-01 12:00 to open end on the configuration
5. Mount device 2 under device 1 from 2025-01-01 12:00 to 2026-01-01 12:00
6. Edit device 1 mount to have an end of 2027-01-01 12:00.

What is the current bug behavior?

The backend responds with an error message:

Object { source: "There is still a ConfigurationDynamicLocationBeginAction or a child mount that is not covered by the updated data.", status: 409, title: "Conflict" } 

What is the expected correct behavior?

The backend should accept the change.

Some logs and/or screenshots

Possible fixes

Maybe the validation on the backend side tests for the wrong time spans.

ToDo's

• Bug reproduced
• Cause found
• Bug fixed