- Notifications
You must be signed in to change notification settings - Fork 2.9k
Labels
netboxseverity: lowDoes not significantly disrupt application functionality, or a workaround is availableDoes not significantly disrupt application functionality, or a workaround is availablestatus: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application
Milestone
Description
NetBox Edition
NetBox Community
NetBox Version
v4.4.4
Python Version
3.12
Steps to Reproduce
- Create a device with a module bay
- Create a module type with an interface
- Create a module of that type in the device
- Delete the module
- Inspect the changelog
Expected Behavior
The changelog entries should be ordered as follows (beginning from step 3 above):
- Create the module
- Create an interface on the module
- Delete the interface
- Delete the module
Observed Behavior
The changelog entries appear as:
- Create the module
- Create an interface on the module
- Delete the module
- Update the interface (appears to be a no-op?)
- Delete the interface
Although the result of the deletion is as expected (both the module and its interface have been removed), the changelog does not accurately reflect the order of operations: In reality, any components of the module are and must be deleted from the database prior to the deletion of the module itself to satisfy foreign key constraints.
It should be noted that similar patterns likely exist elsewhere in the application, where a cascading deletion of dependent objects is not accurately recorded in the changelog. The resolution of this bug should include an audit for all such instances.
Metadata
Metadata
Assignees
Labels
netboxseverity: lowDoes not significantly disrupt application functionality, or a workaround is availableDoes not significantly disrupt application functionality, or a workaround is availablestatus: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application