starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Cable bulk import with ID do not update cables #7764

New Issue
Closed
opened 2025-12-29 20:27:56 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:27:56 +01:00
Owner
Copy Link

Originally created by @clementTal on GitHub (Mar 15, 2023).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.4.5

Python version

3.8

Steps to Reproduce

  1. create a manufacturer using csv:
name,slug
manufacturer,manufacturer
  1. create devicetype using yaml:
manufacturer: manufacturer
model: device_type_model
slug: device_type_model
part_number: ''
u_height: 1.0
is_full_depth: false
subdevice_role: ''
airflow: ''
comments: ''
interfaces:
- name: interface_A
  type: 1000base-t
  mgmt_only: false
  label: ''
  description: ''
  poe_mode: ''
  poe_type: ''
  1. create a device role using csv:
name,slug,color
device_type,device_type,ffffff
  1. create a site using csv:
name,slug,status
site,site,active
  1. create 3 devices using csv:
name,role,manufacturer,device_type,status,site
device_1,device_type,manufacturer,device_type_model,active,site
device_2,device_type,manufacturer,device_type_model,active,site
device_3,device_type,manufacturer,device_type_model,active,site
  1. create a cable to link both created devices interfaces using csv:
side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name
device_1,dcim.interface,interface_A,device_2,dcim.interface,interface_A
  1. get the cable id after creation, and edit the csv to link the cable to other device (replace <CABLE_ID> with correct value):
id,side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name
<CABLE_ID>,device_1,dcim.interface,interface_A,device_3,dcim.interface,interface_A

Expected Behavior

The cable described should be updated

Observed Behavior

Record 1 side_a_name: Side A: device_1 interface_A is already connected

Originally created by @clementTal on GitHub (Mar 15, 2023). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.4.5 ### Python version 3.8 ### Steps to Reproduce 1. create a manufacturer using csv: ``` name,slug manufacturer,manufacturer ``` 2. create devicetype using yaml: ``` manufacturer: manufacturer model: device_type_model slug: device_type_model part_number: '' u_height: 1.0 is_full_depth: false subdevice_role: '' airflow: '' comments: '' interfaces: - name: interface_A type: 1000base-t mgmt_only: false label: '' description: '' poe_mode: '' poe_type: '' ``` 3. create a device role using csv: ``` name,slug,color device_type,device_type,ffffff ``` 4. create a site using csv: ``` name,slug,status site,site,active ``` 5. create 3 devices using csv: ``` name,role,manufacturer,device_type,status,site device_1,device_type,manufacturer,device_type_model,active,site device_2,device_type,manufacturer,device_type_model,active,site device_3,device_type,manufacturer,device_type_model,active,site ``` 6. create a cable to link both created devices interfaces using csv: ``` side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name device_1,dcim.interface,interface_A,device_2,dcim.interface,interface_A ``` 7. get the cable id after creation, and edit the csv to link the cable to other device (replace <CABLE_ID> with correct value): ``` id,side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name <CABLE_ID>,device_1,dcim.interface,interface_A,device_3,dcim.interface,interface_A ``` ### Expected Behavior The cable described should be updated ### Observed Behavior Record 1 side_a_name: Side A: device_1 interface_A is already connected
adam added the type: bugstatus: acceptedtopic: cablingseverity: low labels 2025-12-29 20:27:56 +01:00
adam closed this issue 2025-12-29 20:27:56 +01:00
adam commented 2025-12-29 20:27:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 15, 2023):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Mar 15, 2023): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 20:27:57 +01:00
Author
Owner
Copy Link

@clementTal commented on GitHub (Mar 16, 2023):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

Issue updated with process

@clementTal commented on GitHub (Mar 16, 2023): > Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports. Issue updated with process
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label severity: low status: accepted topic: cabling type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7764
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?