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

Rear port name in Front port export contains excess rear port label which breaks import/update #7685

New Issue
Closed
opened 2025-12-29 20:26:58 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:26:58 +01:00
Owner
Copy Link

Originally created by @jnovak-netsystemcz on GitHub (Feb 26, 2023).

NetBox version

v3.4.5

Python version

3.8

Steps to Reproduce

  1. Create a device 'Device' (fill other mandatory fields on your own)
  2. Create rear port with name 'Port 1' and label 'Test' (fill other mandatory fields on your own)
  3. Create front port with name 'Port 1' and link it to rear port (fill other mandatory fields on your own)
  4. Export front ports of 'Device' with Export->All data (CSV)

Output:

Name,Device,Label,Type,Color,Rear port,Position,Description,ID,Module bay,Module,Mark connected,Cable,Cable Color,Link Peers,Tags,Created,Last updated
Port 1,Device,,8P8C,,Port 1 (Test),1,,453,,,False,,,,,2023-02-26 16:07,2023-02-26 16:07

The issue is that if you would like to import/update data back, text "Port 1 (Test)" is not recognized as rear port name because of excess ' (Test)'.

Expected Behavior

There are two ways how to handle it:

  1. Export just rear port name and ignore label
  2. Export rear port name in one column and rear port label in second column

My personal point of view is that first option is enough.

Observed Behavior

Content of Rear port is combined rear port name and rear port label.

Originally created by @jnovak-netsystemcz on GitHub (Feb 26, 2023). ### NetBox version v3.4.5 ### Python version 3.8 ### Steps to Reproduce 1. Create a device 'Device' (fill other mandatory fields on your own) 2. Create rear port with name 'Port 1' and label 'Test' (fill other mandatory fields on your own) 3. Create front port with name 'Port 1' and link it to rear port (fill other mandatory fields on your own) 4. Export front ports of 'Device' with Export->All data (CSV) Output: ``` Name,Device,Label,Type,Color,Rear port,Position,Description,ID,Module bay,Module,Mark connected,Cable,Cable Color,Link Peers,Tags,Created,Last updated Port 1,Device,,8P8C,,Port 1 (Test),1,,453,,,False,,,,,2023-02-26 16:07,2023-02-26 16:07 ``` The issue is that if you would like to import/update data back, text "Port 1 (Test)" is not recognized as rear port name because of excess ' (Test)'. ### Expected Behavior There are two ways how to handle it: 1. Export just rear port name and ignore label 2. Export rear port name in one column and rear port label in second column My personal point of view is that first option is enough. ### Observed Behavior Content of Rear port is combined rear port name and rear port label.
adam closed this issue 2025-12-29 20:26:58 +01:00
adam commented 2025-12-29 20:26:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 26, 2023):

This is not a bug. You cannot blindly feed exported data into the import form.

@jeremystretch commented on GitHub (Feb 26, 2023): This is not a bug. You cannot blindly feed exported data into the import form.
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
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#7685
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?