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

Reverse for 'sitegroup-trace' not found. 'sitegroup-trace' is not a valid view function or pattern name. #7435

New Issue
Closed
opened 2025-12-29 20:23:28 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:23:28 +01:00
Owner
Copy Link

Originally created by @arthanson on GitHub (Dec 30, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.4.1

Python version

3.8

Steps to Reproduce

  1. Load the demo data (https://github.com/netbox-community/netbox-demo-data)
  2. Go to device "dmi01-akron-rtr01" Interfaces tab
  3. For "GigabitEthernet0/0/0" click the trace button

Expected Behavior

A valid trace should appear

Observed Behavior

NoReverseMatch at /dcim/interfaces/1/trace/
Reverse for 'sitegroup-trace' not found. 'sitegroup-trace' is not a valid view function or pattern name.

Originally created by @arthanson on GitHub (Dec 30, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.4.1 ### Python version 3.8 ### Steps to Reproduce 1. Load the demo data (https://github.com/netbox-community/netbox-demo-data) 2. Go to device "dmi01-akron-rtr01" Interfaces tab 3. For "GigabitEthernet0/0/0" click the trace button ### Expected Behavior A valid trace should appear ### Observed Behavior NoReverseMatch at /dcim/interfaces/1/trace/ Reverse for 'sitegroup-trace' not found. 'sitegroup-trace' is not a valid view function or pattern name.
adam added the type: bugstatus: accepted labels 2025-12-29 20:23:28 +01:00
adam closed this issue 2025-12-29 20:23:28 +01:00
adam commented 2025-12-29 20:23:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 3, 2023):

Seems like we have some corrupt data in the v3.4 demo dump, as the content types for many path objects are invalid. I'll regenerate the demo data.

@jeremystretch commented on GitHub (Jan 3, 2023): Seems like we have some corrupt data in the v3.4 demo dump, as the content types for many path objects are invalid. I'll regenerate the demo data.
adam commented 2025-12-29 20:23:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 3, 2023):

Ok, figured it out. Something in the v3.4 migrations (likely the introduction of a new model) has skewed some of the content type IDs from what they previously defaulted to, resulting in invalid object references within cable paths.

Unfortunately there's no good way to ensure consistent content type IDs with the current import/export process we use to generate the demo data. I'll need to look into this some more. I'm going to close this out and track work toward a solution under this issue as this isn't technically a NetBox bug.

In the interim, you can run manage.py trace_paths --force to rebuild the cable paths after importing the demo data to correct the traces.

@jeremystretch commented on GitHub (Jan 3, 2023): Ok, figured it out. Something in the v3.4 migrations (likely the introduction of a new model) has skewed some of the content type IDs from what they previously defaulted to, resulting in invalid object references within cable paths. Unfortunately there's no good way to ensure consistent content type IDs with the current import/export process we use to generate the demo data. I'll need to look into this some more. I'm going to close this out and track work toward a solution under [this issue](https://github.com/netbox-community/netbox-demo-data/issues/6) as this isn't technically a NetBox bug. In the interim, you can run `manage.py trace_paths --force` to rebuild the cable paths after importing the demo data to correct the traces.
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#7435
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?