Description
When adding a new camera, the system currently allows specifying a model name that does not exist in the configured model list (model-config).
The camera is created successfully even when the provided model name is invalid. This can lead to configuration inconsistencies since the referenced model is not actually available in the system.
The system should validate the provided model name against the available entries in model-config and only allow cameras to be created using valid models.
Environment
- SceneScape Version:
2025.2
- Deployment: Kubernetes
- Component:
manager
- OS: Ubuntu 24.04.3 LTS
Steps to Reproduce
- Deploy SceneScape.
- Navigate to the camera addition interface.
- Attempt to add a camera.
- Provide a model name that does not exist in the
model-config.
- Submit the camera creation request.
Expected Behavior
The system should validate the provided model name against the available models defined in model-config.
If the model does not exist, the system should:
- Reject the request
- Return a validation error indicating that the specified model is invalid.
Example:
Error: Model "<model_name>" is not defined in model-config
Actual Behavior
The camera is created successfully even when the specified model name does not exist in the model-config.
Impact
This behavior allows cameras to be configured with invalid models. As a result:
- The camera is added successfully but no incoming video feed is processed
- No object tracking appears on the GUI
- This creates a confusing system state where the camera exists but is not functional
Ideally, such configurations should be rejected during camera creation instead of allowing an invalid setup.
Additional Context
The issue occurs because there is currently no validation to ensure that the provided model name exists in the configured model list.
Proposed Fix
Add validation to verify that the provided model name exists in model-config. If the model is not found, the request should be rejected with an appropriate validation error.
A fix has been identified and a pull request will be submitted shortly.
Description
When adding a new camera, the system currently allows specifying a model name that does not exist in the configured model list (
model-config).The camera is created successfully even when the provided model name is invalid. This can lead to configuration inconsistencies since the referenced model is not actually available in the system.
The system should validate the provided model name against the available entries in model-config and only allow cameras to be created using valid models.
Environment
2025.2managerSteps to Reproduce
model-config.Expected Behavior
The system should validate the provided model name against the available models defined in
model-config.If the model does not exist, the system should:
Example:
Actual Behavior
The camera is created successfully even when the specified model name does not exist in the
model-config.Impact
This behavior allows cameras to be configured with invalid models. As a result:
Ideally, such configurations should be rejected during camera creation instead of allowing an invalid setup.
Additional Context
The issue occurs because there is currently no validation to ensure that the provided model name exists in the configured model list.
Proposed Fix
Add validation to verify that the provided model name exists in
model-config. If the model is not found, the request should be rejected with an appropriate validation error.A fix has been identified and a pull request will be submitted shortly.