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

Same name VRF on different tenant import conflicts #4578

New Issue
Closed
opened 2025-12-29 18:37:52 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:37:52 +01:00
Owner
Copy Link

Originally created by @Omripresent on GitHub (Feb 18, 2021).

Environment

  • Python version: 3.8.7
  • NetBox version: 2.10.4

Steps to Reproduce

Scenario A:

  1. Create 2 or more VRFs with the same name under different tenants
  2. Try to import prefixes into one of the tenants and VRFs
  3. The following error will show:
    vrf: "VRF_NAME" is not a unique value in this field; multiple objects were found

Scenario B:

  1. Create 2 or more VRFs with the same name under different tenants
  2. Create a new prefix manually
  3. Under the VRF selection the same name will show up multiple times without tenant identification

Expected Behavior

Scenario A:
Using the tenant column on the prefix import page should associate with the VRF lookup

Scenario B:
The VRF dropdown list should include the tenant with the name of the VRF, for example: TENANT_NAME // VRF_NAME
or the tenant selection in the form should filter out VRFs not belonging to the selected tenant

Observed Behavior

Inability to bulk import prefixes where same VRF names are used
Uncertainty of VRF selection in the prefix edit page

Originally created by @Omripresent on GitHub (Feb 18, 2021). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reporting reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions 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, and that any plugins have been disabled. --> ### Environment * Python version: 3.8.7 * NetBox version: 2.10.4 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. 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 client library such as pynetbox. --> ### Steps to Reproduce Scenario A: 1. Create 2 or more VRFs with the same name under different tenants 2. Try to import prefixes into one of the tenants and VRFs 3. The following error will show: vrf: "VRF_NAME" is not a unique value in this field; multiple objects were found Scenario B: 1. Create 2 or more VRFs with the same name under different tenants 2. Create a new prefix manually 3. Under the VRF selection the same name will show up multiple times without tenant identification <!-- What did you expect to happen? --> ### Expected Behavior Scenario A: Using the tenant column on the prefix import page should associate with the VRF lookup Scenario B: The VRF dropdown list should include the tenant with the name of the VRF, for example: TENANT_NAME // VRF_NAME or the tenant selection in the form should filter out VRFs not belonging to the selected tenant <!-- What happened instead? --> ### Observed Behavior Inability to bulk import prefixes where same VRF names are used Uncertainty of VRF selection in the prefix edit page
adam closed this issue 2025-12-29 18:37:52 +01:00
adam commented 2025-12-29 18:37:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 23, 2021):

Use a unique identifier for each VRF, such as its route distinguisher or database ID.

@jeremystretch commented on GitHub (Feb 23, 2021): Use a unique identifier for each VRF, such as its route distinguisher or database ID.
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#4578
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?