Bug #15656
closed
[API] container requests can have broken references to containers
Added by Peter Amstutz about 5 years ago.
Updated about 5 years ago.
Release relationship:
Auto
Description
The database does not enforce foreign key consistency on the container_uuid column. It is possible to delete a container that has container requests referring to it. If a container request has a reference to a container record that no longer exists, clients such as workbench break badly.
Related, it is intended that normal (non-admin) users cannot delete container records, but that may be missing a permission check.
- Status changed from New to In Progress
- Description updated (diff)
- Status changed from In Progress to New
- Status changed from New to In Progress
- Assigned To set to Tom Clegg
- Target version changed from To Be Groomed to 2019-10-09 Sprint
Other than that, this LGTM.
15656-user-delete-container @ d22da8c4ae59fa50bfecaf3c5857fe8c0cc5fae7
"This API requires admin privileges. In normal operation, it should not be used at all. API clients like Workbench might not work correctly when a container request references a container that has been deleted."
- Status changed from In Progress to Resolved
Also available in: Atom
PDF