Assigning prefixes from a container unique across all VRFs

[avolmensky]

Deployment Type

Self-hosted

Triage priority

I volunteer to perform this work (if approved)

NetBox Version

v4.1.1

Python Version

3.10

Steps to Reproduce

Create a container
Assign prefix from container in a vrf
Assign prefix from container again in global VRF

Expected Behavior

Assigned global prefix shouldn't overlap with prefix in VRF (or at least we should have the option to specify somewhere)

Observed Behavior

Assigned global prefix overlaps with prefix in VRF

[avolmensky]

Summary

We use a lot of route leaking between VRFs and use public addressing to maintain unique addressing between VRFs. I have recently updated from Netbox version 3.2.2 and this behavior has changed.

Details

Previously, I understood that containers functioned as described in issue #1073, but it looks like #10109 (Commit 7ba0b42) has changed this behavior.

For now I am running the fix contained in #14776 (comment) and it is working fine

Request

I can see use cases for the behavior of both. Does anything in the current version of Netbox allow us to specify how we want a container to assign prefixes? If not is it possible to add an option to configuration.py (or something similar) to change the behavior of this?

I'm happy to submit a PR if needed

[jeremystretch]

Thank you for opening a bug report. 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.