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

Prefixes list from Aggregates list does not work #6933

New Issue
Closed
opened 2025-12-29 19:46:56 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:46:56 +01:00
Owner
Copy Link

Originally created by @zuokot on GitHub (Sep 5, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.3.2

Python version

3.8

Steps to Reproduce

Add Aggregate 192.168.0.0/21
Add Prefix 192.168.0.0/24
Go to Aggregates and open the Aggregate 192.168.0.0/21, and then click "Prefixes"

Expected Behavior

There should be a list of prefixes beloging to 192.168.0.0/21, in this case 192.168.0.0/24

By creating additional "Container" status type of prefix 192.168.0.0/21, there is the expected behavior.

Observed Behavior

The outcome is:

Server Error
There was a problem with your request. Please contact an administrator.

The complete exception is provided below:

<class 'django.urls.exceptions.NoReverseMatch'>

Reverse for 'prefix' with arguments '(None,)' not found. 1 pattern(s) tried: ['ipam/prefixes/(?P[0-9]+)/\Z']

Python version: 3.8.10
NetBox version: 3.3.2

By creating additional "Container" status type of prefix 192.168.0.0/21, there is the expected behavior.
prefix_error

Originally created by @zuokot on GitHub (Sep 5, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.3.2 ### Python version 3.8 ### Steps to Reproduce Add Aggregate 192.168.0.0/21 Add Prefix 192.168.0.0/24 Go to Aggregates and open the Aggregate 192.168.0.0/21, and then click "Prefixes" ### Expected Behavior There should be a list of prefixes beloging to 192.168.0.0/21, in this case 192.168.0.0/24 By creating additional "Container" status type of prefix 192.168.0.0/21, there is the expected behavior. ### Observed Behavior The outcome is: -------- Server Error There was a problem with your request. Please contact an administrator. The complete exception is provided below: <class 'django.urls.exceptions.NoReverseMatch'> Reverse for 'prefix' with arguments '(None,)' not found. 1 pattern(s) tried: ['ipam/prefixes/(?P<pk>[0-9]+)/\\Z'] Python version: 3.8.10 NetBox version: 3.3.2 --------- By creating additional "Container" status type of prefix 192.168.0.0/21, there is the expected behavior. ![prefix_error](https://user-images.githubusercontent.com/91075161/188440343-750b2309-4936-4975-8b26-b4f1acb8a0b1.PNG)
adam added the type: bugstatus: accepted labels 2025-12-29 19:46:56 +01:00
adam closed this issue 2025-12-29 19:46:56 +01:00
adam commented 2025-12-29 19:46:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 6, 2022):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.3.2. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@jeremystretch commented on GitHub (Sep 6, 2022): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.3.2. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.
adam commented 2025-12-29 19:46:57 +01:00
Author
Owner
Copy Link

@tinyt777 commented on GitHub (Sep 6, 2022):

I updated to 3.3.2 yesterday and am now seeing this behavior on some prefixes, though not all. I'm still looking for a pattern. Here's a small sample of our structure.

image

If I then select either the 10.0.0.0/8 prefix or the 10.0.0.0/13 prefix and then select the child prefixes tab, I get the same error provided by @zuokot

image
image

EDIT:
I'm also attaching the error I've extracted from the server that provides the full traceback.
netbox_10259_error.txt

@tinyt777 commented on GitHub (Sep 6, 2022): I updated to 3.3.2 yesterday and am now seeing this behavior on some prefixes, though not all. I'm still looking for a pattern. Here's a small sample of our structure. ![image](https://user-images.githubusercontent.com/63061459/188659904-5a404a61-4180-4b91-977e-4bfc20eb10db.png) If I then select either the 10.0.0.0/8 prefix or the 10.0.0.0/13 prefix and then select the child prefixes tab, I get the same error provided by @zuokot ![image](https://user-images.githubusercontent.com/63061459/188660272-737ca134-d35a-4a20-9000-3b648512ec4c.png) ![image](https://user-images.githubusercontent.com/63061459/188660310-fea0af50-eb02-438d-86a2-363dff0ed288.png) EDIT: I'm also attaching the error I've extracted from the server that provides the full traceback. [netbox_10259_error.txt](https://github.com/netbox-community/netbox/files/9499458/netbox_10259_error.txt)
adam commented 2025-12-29 19:46:57 +01:00
Author
Owner
Copy Link

@zuokot commented on GitHub (Sep 7, 2022):

Hi,
Interesting founding which corrected the issue.
On the "Prefixes" page there is for some reason a header column "Prefix (flat)" chosen instead of "Prefix" and as soon as changed it back to "Prefix", the problem disappeared.

prefixes_headers

@zuokot commented on GitHub (Sep 7, 2022): Hi, Interesting founding which corrected the issue. On the "Prefixes" page there is for some reason a header column "Prefix (flat)" chosen instead of "Prefix" and as soon as changed it back to "Prefix", the problem disappeared. ![prefixes_headers](https://user-images.githubusercontent.com/91075161/188913652-58ff5593-ad41-4b21-affb-56ba577bc490.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 status: accepted type: bug
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#6933
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?