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

Prefix with role container does not show child prefixes correctly #2916

New Issue
Closed
opened 2025-12-29 18:23:22 +01:00 by adam · 6 comments
adam commented 2025-12-29 18:23:22 +01:00
Owner
Copy Link

Originally created by @ziggekatten on GitHub (Sep 29, 2019).

Environment

  • Python version: 3.7.4
  • NetBox version: 2.6.5

Steps to Reproduce

  1. Add a prefix of type container 192.168.125.0/24
  2. Add a prefix of type Active 192.168.125.0/26
  3. Add a prefix of type Active 192.168.125.64/26
  4. Edit prefix 192.168.125.0/26 and assign to a VRF
  5. Edit prefix 192.168.125.64/26 and assign to another VRF

Expected Behavior

Adding two prefixes with assignment to separate VFRs:

192.168.125.0/24 and 192.168.125.64/26

In the prefixes UI I should now see the 192.168.1.0/24 with an small arrow indicating child prefixes

Klickin on the container prefix, i should have twe child prefixes

Capture1

Observed Behavior

As soon as I add one or the other prefix to a VRF, the prefix are not hidden under the container, it shows directly in the UI. Klicking on the container prefix however, shows (correctly) that there are two child prefixes.
Capture2

Capture3

Originally created by @ziggekatten on GitHub (Sep 29, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7.4 <!-- Example: 3.5.4 --> * NetBox version: 2.6.5<!-- Example: 2.5.2 --> <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Add a prefix of type container 192.168.125.0/24 2. Add a prefix of type Active 192.168.125.0/26 3. Add a prefix of type Active 192.168.125.64/26 4. Edit prefix 192.168.125.0/26 and assign to a VRF 5. Edit prefix 192.168.125.64/26 and assign to another VRF <!-- What did you expect to happen? --> ### Expected Behavior Adding two prefixes with assignment to separate VFRs: 192.168.125.0/24 and 192.168.125.64/26 In the prefixes UI I should now see the 192.168.1.0/24 with an small arrow indicating child prefixes Klickin on the container prefix, i should have twe child prefixes ![Capture1](https://user-images.githubusercontent.com/55629049/65830986-a878f200-e2b4-11e9-9558-c6c27ef18ced.PNG) <!-- What happened instead? --> ### Observed Behavior As soon as I add one or the other prefix to a VRF, the prefix are not hidden under the container, it shows directly in the UI. Klicking on the container prefix however, shows (correctly) that there are two child prefixes. ![Capture2](https://user-images.githubusercontent.com/55629049/65830991-b6c70e00-e2b4-11e9-98e3-20b1c6c9f594.PNG) ![Capture3](https://user-images.githubusercontent.com/55629049/65830992-bc245880-e2b4-11e9-85d1-e3c2460284ed.PNG)
adam closed this issue 2025-12-29 18:23:23 +01:00
adam commented 2025-12-29 18:23:23 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Sep 30, 2019):

Allow indicator for child prefixes appears in prefixes list when same VRF is assigned to them.
What you want to do can be defined in Aggregate menu.
Try to create Aggregate with 192.168.125.0/24. Then assign 192.168.125.0/26 as VRF 10700 and 192.168.125.64/26 as VRF 10710 in the aggregate.

@kobayashi commented on GitHub (Sep 30, 2019): Allow indicator for child prefixes appears in prefixes list when same VRF is assigned to them. What you want to do can be defined in Aggregate menu. Try to create Aggregate with 192.168.125.0/24. Then assign 192.168.125.0/26 as VRF 10700 and 192.168.125.64/26 as VRF 10710 in the aggregate.
adam commented 2025-12-29 18:23:23 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Sep 30, 2019):

No, that does not solve the issue. As a service provider, we have several clients using the same 10.0.0.0/8 and 192.168.0.0/16, and aggregates can NOT have the same prefix more than once.

@ziggekatten commented on GitHub (Sep 30, 2019): No, that does not solve the issue. As a service provider, we have several clients using the same 10.0.0.0/8 and 192.168.0.0/16, and aggregates can NOT have the same prefix more than once.
adam commented 2025-12-29 18:23:24 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Oct 1, 2019):

Thanks to let me know about the detail.
I tested today with netbox version 2.6.5 and found that worked well.
Screenshot from 2019-09-30 22-20-45

Which netbox version are you using right now? So I can try with your version.

@kobayashi commented on GitHub (Oct 1, 2019): Thanks to let me know about the detail. I tested today with netbox version 2.6.5 and found that worked well. ![Screenshot from 2019-09-30 22-20-45](https://user-images.githubusercontent.com/8712070/65929561-9b512580-e3d0-11e9-96a2-25a8a2b5606d.png) Which netbox version are you using right now? So I can try with your version.
adam commented 2025-12-29 18:23:24 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Oct 1, 2019):

I’m running 2.6.5

@ziggekatten commented on GitHub (Oct 1, 2019): I’m running 2.6.5
adam commented 2025-12-29 18:23:24 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Oct 1, 2019):

OK, I found this is reproduced not by one by one each but only by bulk importing.
Also found the same issue is already opened #2562. Please track that case.

@kobayashi commented on GitHub (Oct 1, 2019): OK, I found this is reproduced not by one by one each but only by bulk importing. Also found the same issue is already opened #2562. Please track that case.
adam commented 2025-12-29 18:23:24 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Oct 1, 2019):

closed this issue due to duplication. Please refer #2562

@kobayashi commented on GitHub (Oct 1, 2019): closed this issue due to duplication. Please refer #2562
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#2916
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?