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

Not able to specify multiple terminations for either end of a cable when bulk importing using the CSV method #9480

New Issue
Closed
opened 2025-12-29 20:50:28 +01:00 by adam · 6 comments
adam commented 2025-12-29 20:50:28 +01:00
Owner
Copy Link

Originally created by @netravnen on GitHub (Apr 15, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.4

Python Version

3.11

Steps to Reproduce

  1. Create a LC patch panel (Generic/LC-24-port-fiber-patch-panel-half-depth)
  2. Create a SC patch panel (Generic/SC-24-port-fiber-patch-panel-half-depth)
  3. Run the CSV importer with the following data (only the required fields mentioned here) 
    side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name
PP1,dcim.frontport,Port 2,PP2,dcim.frontport,"11,12"
  4. B-side here is a double port in an SC panel. Each side marked with its own number.
    image
  5. A-side is your typical 24-port LC patch panel.

Expected Behavior

Importer should succed. Used the exact same format the CSV data exporter outputs for the Cable (if created manually in the Web-UI).

Observed Behavior

The bulk importer fails the creation of the cable. ⛔

image

Creating of the same cable using the Web-UI wizard successfully completes the cable creation. ✅

image

I use the CSV format for the importer.

Originally created by @netravnen on GitHub (Apr 15, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.4 ### Python Version 3.11 ### Steps to Reproduce 1. Create a LC patch panel ([Generic/LC-24-port-fiber-patch-panel-half-depth](https://github.com/netbox-community/devicetype-library/blob/master/device-types/Generic/LC-24-port-fiber-patch-panel-half-depth.yaml)) 2. Create a SC patch panel ([Generic/SC-24-port-fiber-patch-panel-half-depth](https://github.com/netbox-community/devicetype-library/blob/master/device-types/Generic/SC-24-port-fiber-patch-panel-half-depth.yaml)) 3. Run the CSV importer with the following data (only the required fields mentioned here) ``` side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name PP1,dcim.frontport,Port 2,PP2,dcim.frontport,"11,12" ``` 4. B-side here is a double port in an SC panel. Each side marked with its own number. ![image](https://github.com/netbox-community/netbox/assets/1938389/616a1d85-a51a-4175-b64f-4015bc85fa01) 5. A-side is your typical 24-port LC patch panel. ### Expected Behavior Importer should succed. Used the exact same format the CSV data exporter outputs for the Cable (if created manually in the Web-UI). ### Observed Behavior The bulk importer fails the creation of the cable. ⛔ ![image](https://github.com/netbox-community/netbox/assets/1938389/1822755b-0d94-479b-9be0-cc2ab88b601e) Creating of the same cable using the Web-UI wizard successfully completes the cable creation. ✅ ![image](https://github.com/netbox-community/netbox/assets/1938389/47abeb38-4d37-4570-99c0-d470a5baa7bc) I use the CSV format for the importer.
adam closed this issue 2025-12-29 20:50:28 +01:00
adam commented 2025-12-29 20:50:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 29, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 29, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:50:29 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 29, 2024):

I too suffer from this. Is there another case of bulk import that supports many-to-one imports ? I would volunteer to fix this bug if there is.

@jsenecal commented on GitHub (Jul 29, 2024): I too suffer from this. Is there another case of bulk import that supports many-to-one imports ? I would volunteer to fix this bug if there is.
adam commented 2025-12-29 20:50:30 +01:00
Author
Owner
Copy Link

@netravnen commented on GitHub (Jul 29, 2024):

I too suffer from this. Is there another case of bulk import that supports many-to-one imports ? I would volunteer to fix this bug if there is.

@jsenecal I would guess using the REST API to create the objects works. I have not tested this.

@netravnen commented on GitHub (Jul 29, 2024): > I too suffer from this. Is there another case of bulk import that supports many-to-one imports ? I would volunteer to fix this bug if there is. @jsenecal I would _guess_ using the REST API to create the objects works. I have not tested this.
adam commented 2025-12-29 20:50:30 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 29, 2024):

I too suffer from this. Is there another case of bulk import that supports many-to-one imports ? I would volunteer to fix this bug if there is.

@jsenecal I would guess using the REST API to create the objects works. I have not tested this.

The REST API is not on topic here. I'm asking about another model that uses the CSV importer the right way with many-to-one relations

@jsenecal commented on GitHub (Jul 29, 2024): > > I too suffer from this. Is there another case of bulk import that supports many-to-one imports ? I would volunteer to fix this bug if there is. > > @jsenecal I would _guess_ using the REST API to create the objects works. I have not tested this. The REST API is not on topic here. I'm asking about another model that uses the CSV importer _the right way_ with many-to-one relations
adam commented 2025-12-29 20:50:30 +01:00
Author
Owner
Copy Link

@netravnen commented on GitHub (Jul 29, 2024):

Is there another case of bulk import that supports many-to-one imports

Afaik, no.

I use CSV importing for data to a certain extent for several object types.

I only ran into this issue when LC / SC panels assigned numbers for all positions on the panel.

@netravnen commented on GitHub (Jul 29, 2024): > Is there another case of bulk import that supports many-to-one imports Afaik, no. I use CSV importing for data to a certain extent for several object types. I only ran into this issue when LC / SC panels assigned numbers for _all_ positions on the panel.
adam commented 2025-12-29 20:50:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 11, 2024):

Closing this out as stale as no one has volunteered to own the work.

@jeremystretch commented on GitHub (Sep 11, 2024): Closing this out as stale as no one has volunteered to own the work.
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 pending closure severity: low status: needs owner 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#9480
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?