Importing duplicate cable raises error "Cable has no termination_a_type" #3028

Closed
opened 2025-12-29 18:24:54 +01:00 by adam · 0 comments
Owner

Originally created by @sulisu on GitHub (Nov 22, 2019).

Environment

  • Python version: 3.5.3
  • NetBox version: 2.6.7

Steps to Reproduce

  1. Import a cable between two interface, which already exist in netbox
    Example Data
side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name,type,status
ZBP06U0708,interface,port3,ZBP06S6520X1,interface,XGE1/0/2,Multimode Fiber (OM3),Planned

It will sucess at first time when there is no same cable definition in netbox

  1. Import the above csv data again
<class 'dcim.models.Cable.termination_a_type.RelatedObjectDoesNotExist'>

Cable has no termination_a_type.

Expected Behavior

A more clear error definition, which indicate there is a duplicate, will be very helpful.

Observed Behavior

An error message seems not relating to the real problem.

Originally created by @sulisu on GitHub (Nov 22, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5.3 * NetBox version: 2.6.7 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Import a cable between two interface, which already exist in netbox Example Data ``` side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name,type,status ZBP06U0708,interface,port3,ZBP06S6520X1,interface,XGE1/0/2,Multimode Fiber (OM3),Planned ``` It will sucess at first time when there is no same cable definition in netbox 2. Import the above csv data again ``` <class 'dcim.models.Cable.termination_a_type.RelatedObjectDoesNotExist'> Cable has no termination_a_type. ``` <!-- What did you expect to happen? --> ### Expected Behavior A more clear error definition, which indicate there is a duplicate, will be very helpful. <!-- What happened instead? --> ### Observed Behavior An error message seems not relating to the real problem.
adam added the type: bugstatus: accepted labels 2025-12-29 18:24:54 +01:00
adam closed this issue 2025-12-29 18:24:54 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3028