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

VRF information lost during Import/Export of Prefix #2813

New Issue
Closed
opened 2025-12-29 18:22:24 +01:00 by adam · 5 comments
adam commented 2025-12-29 18:22:24 +01:00
Owner
Copy Link

Originally created by @xjs678qr on GitHub (Aug 19, 2019).

Environment

  • Python version: 2.7.15+
  • NetBox version: 2.6.2

Steps to Reproduce

  1. Create a VRF (named 10DMZ in my case)
  2. Create a Prefix beloning to the VRF (e.g. 10.210.0.0/21)
  3. Export the Prefixes to CSV. In the Export, the VRF column is empty.

Reversely,

  1. import a list of Prefixes and fill out the existing VRF
  2. The iùmport succeeds, but the prefixes are assigned to the 'GLOBAL' table

Expected Behavior

VRF information to be present in the CSV during export

VRF Information to be taken into account during import

Observed Behavior

VRF information is missing the exported CSV

VRF information during import is ignored.

Originally created by @xjs678qr on GitHub (Aug 19, 2019). ### Environment * Python version: 2.7.15+ * NetBox version: 2.6.2 ### Steps to Reproduce 1. Create a VRF (named 10DMZ in my case) 2. Create a Prefix beloning to the VRF (e.g. 10.210.0.0/21) 3. Export the Prefixes to CSV. In the Export, the VRF column is empty. Reversely, 1. import a list of Prefixes and fill out the existing VRF 2. The iùmport succeeds, but the prefixes are assigned to the 'GLOBAL' table ### Expected Behavior VRF information to be present in the CSV during export VRF Information to be taken into account during import <!-- What happened instead? --> ### Observed Behavior VRF information is missing the exported CSV VRF information during import is ignored.
adam added the type: bugstatus: accepted labels 2025-12-29 18:22:24 +01:00
adam closed this issue 2025-12-29 18:22:24 +01:00
adam commented 2025-12-29 18:22:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 20, 2019):

Python version: 2.7.15+

Please specify your actual Python version.

@jeremystretch commented on GitHub (Aug 20, 2019): > Python version: 2.7.15+ Please specify your actual Python version.
adam commented 2025-12-29 18:22:25 +01:00
Author
Owner
Copy Link

@xjs678qr commented on GitHub (Aug 20, 2019):

It states literally 2.7.15+:

$ python -V
Python 2.7.15+

@xjs678qr commented on GitHub (Aug 20, 2019): It states literally 2.7.15+: $ python -V Python 2.7.15+
adam commented 2025-12-29 18:22:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 20, 2019):

NetBox 2.5 and later requires Python 3.5 or higher. Please verify the version of Python under which NetBox is running.

@jeremystretch commented on GitHub (Aug 20, 2019): NetBox 2.5 and later requires Python 3.5 or higher. Please verify the version of Python under which NetBox is running.
adam commented 2025-12-29 18:22:25 +01:00
Author
Owner
Copy Link

@xjs678qr commented on GitHub (Aug 21, 2019):

Indeed, it's python3:

$python3 -V
Python 3.6.8

@xjs678qr commented on GitHub (Aug 21, 2019): Indeed, it's python3: $python3 -V Python 3.6.8
adam commented 2025-12-29 18:22:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 25, 2019):

The issue here is that the default CSV generator outputs the VRF RD only (which used to be a required field), so if a VRF does not have an RD assigned, the column will be empty. We should probably change it to output the VRF name instead of the RD to ensure consistency.

@jeremystretch commented on GitHub (Sep 25, 2019): The issue here is that the default CSV generator outputs the VRF RD only (which used to be a required field), so if a VRF does not have an RD assigned, the column will be empty. We should probably change it to output the VRF name instead of the RD to ensure consistency.
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: accepted 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#2813
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?