Prefix import with VRF information is not possible when RD is not configured #2940
Labels
status: accepted
This issue has been accepted for implementation
type: bug
A confirmed report of unexpected behavior in the application
Environment
Steps to Reproduce
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."
The text was updated successfully, but these errors were encountered: