Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefix import with VRF information is not possible when RD is not configured #2940

Closed
markkuleinio opened this issue Feb 28, 2019 · 1 comment
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@markkuleinio
Copy link
Contributor

Environment

  • Python version: 3.5.3
  • NetBox version: 2.5.7

Steps to Reproduce

  1. Go to prefix import
  2. vrf field requires VRF RD, the VRF name is not usable
  3. Import to the correct VRF is not possible if VRF does not have RD configured

Expected Behavior

It should be possible to use either the internal ID of the VRF (shown in the URL as in /ipam/vrfs/4/) or the VRF name in the vrf field.

Observed Behavior

If trying to use VRF name or ID in the vrf field: "Row 1 vrf: VRF not found."

@DanSheps DanSheps added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation labels Feb 28, 2019
@jeremystretch
Copy link
Member

Can't use VRF name as it's not guaranteed to be unique. Will have to enable using the primary key as we do for unnamed devices.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants