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

Parent Prefix in Global with Child Prefix in VRF creates orphan Prefix #318

New Issue
Closed
opened 2025-12-29 16:20:49 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:20:49 +01:00
Owner
Copy Link

Originally created by @DanSheps on GitHub (Aug 2, 2016).

When adding child prefixes to parent prefixes where the child is in a separate VRF then the parent, this causes a orphan prefix where the only access to it is through that VRF. The orphan prefix isn't visible in the prefix list, because the prefix list table considers it a child even though it is in a different VRF.

I ran into this where I placed a parent prefix (/22) in the global VRF, because it isn't assigned to any one single VRF and then put in the child prefix in the individual VRF's.

I am assuming this is based on the fact that you determine a child/parent relationship by VRF and prefix.
#395 discusses changing the functionality of the global prefix, and this is a separate issue from that

Originally created by @DanSheps on GitHub (Aug 2, 2016). When adding child prefixes to parent prefixes where the child is in a separate VRF then the parent, this causes a orphan prefix where the only access to it is through that VRF. The orphan prefix isn't visible in the prefix list, because the prefix list table considers it a child even though it is in a different VRF. I ran into this where I placed a parent prefix (/22) in the global VRF, because it isn't assigned to any one single VRF and then put in the child prefix in the individual VRF's. I am assuming this is based on the fact that you determine a child/parent relationship by VRF and prefix. #395 discusses changing the functionality of the global prefix, and this is a separate issue from that
adam added the status: duplicate label 2025-12-29 16:20:49 +01:00
adam closed this issue 2025-12-29 16:20:50 +01:00
adam commented 2025-12-29 16:20:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 2, 2016):

This will be covered by whatever work is done to resolve #395 so I'm going to mark this as a duplicate.

@jeremystretch commented on GitHub (Aug 2, 2016): This will be covered by whatever work is done to resolve #395 so I'm going to mark this as a duplicate.
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: duplicate
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#318
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?