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

Child Prefix is displayed under wrong parent when using VRFs #7201

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

Originally created by @the-rubikscube on GitHub (Nov 4, 2022).

NetBox version

v3.3.7 (docker)

Python version

3.10

Steps to Reproduce

  1. Create 2 VRFs, e.g. vrf1 and vrf2
  2. For each VRF, create a Prefix and a child prefix with the same IP addresses, e.g. 1.1.0.0/16 for parent and 1.1.1.0/24 for child
  3. Navigate to the Prefix view. If not already enabled, adjust the settings so depth indicators are shown

Expected Behavior

In the prefix overview, the child prefixes should be listed under their corresponding parent, taking the VRF assignment into account.

Observed Behavior

Both child prefixes are shown below the second parent prefix, although the child count on the parents is correct.
grafik

Originally created by @the-rubikscube on GitHub (Nov 4, 2022). ### NetBox version v3.3.7 (docker) ### Python version 3.10 ### Steps to Reproduce 1. Create 2 VRFs, e.g. vrf1 and vrf2 2. For each VRF, create a Prefix and a child prefix with the same IP addresses, e.g. 1.1.0.0/16 for parent and 1.1.1.0/24 for child 3. Navigate to the Prefix view. If not already enabled, adjust the settings so depth indicators are shown ### Expected Behavior In the prefix overview, the child prefixes should be listed under their corresponding parent, taking the VRF assignment into account. ### Observed Behavior Both child prefixes are shown below the second parent prefix, although the child count on the parents is correct. ![grafik](https://user-images.githubusercontent.com/115145568/199989102-28cc977c-f226-4518-906d-021ec69a320c.png)
adam closed this issue 2025-12-29 20:20:24 +01:00
adam commented 2025-12-29 20:20:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 10, 2022):

You're seeing this because you've ordered the list by prefix value (note the arrow next to the "Prefix" heading). You can clear this by clicking the red X in the column header. By default, prefixes are ordered by VRF:

Screenshot 2022-11-10 at 16-43-07 Prefixes NetBox

@jeremystretch commented on GitHub (Nov 10, 2022): You're seeing this because you've ordered the list by prefix value (note the arrow next to the "Prefix" heading). You can clear this by clicking the red X in the column header. By default, prefixes are ordered by VRF: ![Screenshot 2022-11-10 at 16-43-07 Prefixes NetBox](https://user-images.githubusercontent.com/13487278/201212016-329855eb-e442-4d8d-b7af-67b19573477e.png)
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
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#7201
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?