-
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.10
Steps to Reproduce
- Create a device, dmi-albany-rtr01, with Interfaces GigabitEthernet0/1/4 and GigabitEthernet0/1/5 in site "DM-Albany
- Bulk upload the following data:
side_a_device, side_a_type, side_a_name, side_b_device, side_b_type, side_b_name, side_a_site, side_b_site, status
"dmi01-albany-rtr01", "dcim.interface", "GigabitEthernet0/1/4", "dmi01-albany-rtr01", "dcim.interface", "GigabitEthernet0/1/5", "DM-Albany", "DM-Albany", ""
Note the status field isn't marked as mandatory but SHOULD be to be consistent with the UI
Expected Behavior
Upload is rejected as "" is not a valid status choice (the UI enforces a valid value being set)
Observed Behavior
Cable is allowed to be created with the below data
The larger issue here is around netbox-branching - if in a branch and this action is undertake, the branch will fail to merge or in main fail to sync due to a validation error of status must be set
pjlarmstrong, nbl-csling and clovehitch
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