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

Bulk import of prefixes fails when VLAN id is defined more than once #9040

New Issue
Closed
opened 2025-12-29 20:44:40 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:44:40 +01:00
Owner
Copy Link

Originally created by @garryshtern on GitHub (Jan 4, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.6.3

Python Version

3.9

Steps to Reproduce

Create two instances of the same VLAN
Try bulk import of a prefix with above vlan populated in vid field

Expected Behavior

Use additional details in the import to distinguish between different vlan. Perhaps, tenant, site, etc.

Observed Behavior

Import fails with “record value not unique.

Originally created by @garryshtern on GitHub (Jan 4, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.6.3 ### Python Version 3.9 ### Steps to Reproduce Create two instances of the same VLAN Try bulk import of a prefix with above vlan populated in vid field ### Expected Behavior Use additional details in the import to distinguish between different vlan. Perhaps, tenant, site, etc. ### Observed Behavior Import fails with “record value <vlan> not unique.
adam added the type: bugstatus: revisions needed labels 2025-12-29 20:44:40 +01:00
adam closed this issue 2025-12-29 20:44:40 +01:00
adam commented 2025-12-29 20:44:41 +01:00
Author
Owner
Copy Link

@markkuleinio commented on GitHub (Jan 5, 2024):

This works for me on 3.7.0:

prefix,status,vlan,site
10.1.1.0/24,active,100,Site1
10.1.2.0/24,active,100,Site2

(Both sites have VLAN 100 separately)

image
@markkuleinio commented on GitHub (Jan 5, 2024): This works for me on 3.7.0: ``` prefix,status,vlan,site 10.1.1.0/24,active,100,Site1 10.1.2.0/24,active,100,Site2 ``` (Both sites have VLAN 100 separately) <img width="751" alt="image" src="https://github.com/netbox-community/netbox/assets/25136274/e7c1f944-1fd6-49df-9641-ffe7c666cf02">
adam commented 2025-12-29 20:44:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 5, 2024):

@garryshtern could you please expand on your reproduction steps above to specify exactly what objects your creating at each step, so that someone else can reliably replicate the behavior?

@jeremystretch commented on GitHub (Jan 5, 2024): @garryshtern could you please expand on your reproduction steps above to specify **exactly** what objects your creating at each step, so that someone else can reliably replicate the behavior?
adam commented 2025-12-29 20:44:41 +01:00
Author
Owner
Copy Link

@garryshtern commented on GitHub (Jan 7, 2024):

I created two VLAN 100s under demo.netbox.com. Now, go here: https://demo.netbox.dev/ipam/prefixes/import/, and try to import the following:
"prefix","tenant","site","vlan","status"
"1.1.1.0/24","Initech","DM-NYC",100,"active"

You should see an error:
image

@garryshtern commented on GitHub (Jan 7, 2024): I created two VLAN 100s under demo.netbox.com. Now, go here: https://demo.netbox.dev/ipam/prefixes/import/, and try to import the following: "prefix","tenant","site","vlan","status" "1.1.1.0/24","Initech","DM-NYC",100,"active" You should see an error: <img width="349" alt="image" src="https://github.com/netbox-community/netbox/assets/6483893/136f2549-fc8b-49df-9953-fdc6bada0979">
adam commented 2025-12-29 20:44:43 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jan 7, 2024):

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.

@abhi1693 commented on GitHub (Jan 7, 2024): 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:44:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 24, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Jan 24, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 status: revisions needed 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#9040
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?