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

Trace Splits are returned for 1:1 connections #3617

New Issue
Closed
opened 2025-12-29 18:30:11 +01:00 by adam · 0 comments
adam commented 2025-12-29 18:30:11 +01:00
Owner
Copy Link

Originally created by @abrahamvegh on GitHub (Apr 28, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.7.3
  • NetBox version: 2.8.1

Steps to Reproduce

  1. Configure devices representing the following connections:
    Interface <-> Cable <-> Front Port <-> Rear Port <-> Cable <-> Interface
    In my specific example, this would be Cat6 connections from a switch port through a patch panel to a wireless AP.
  2. Trace the connection from either of the Interfaces.

Expected Behavior

The full connection is traced from end to end.

Observed Behavior

A ‘Trace Split’ error is produced after the first cable, but the list only contains a single option for continuing the trace.

Screen Shot 2020-04-27 at 11 48 36 PM

I believe this was introduced as part of the changes in #4388. This may be a further regression of that bug.

EDIT: This only occurs when tracing from the Interface connected to the Rear Port. When tracing through the Front Port, the entire trace completes successfully.

Originally created by @abrahamvegh on GitHub (Apr 28, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. 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, and that any plugins have been disabled. --> ### Environment * Python version: 3.7.3 * NetBox version: 2.8.1 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. 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 client library such as pynetbox. --> ### Steps to Reproduce 1. Configure devices representing the following connections: `Interface <-> Cable <-> Front Port <-> Rear Port <-> Cable <-> Interface` In my specific example, this would be Cat6 connections from a switch port through a patch panel to a wireless AP. 2. Trace the connection from either of the Interfaces. <!-- What did you expect to happen? --> ### Expected Behavior The full connection is traced from end to end. <!-- What happened instead? --> ### Observed Behavior A ‘Trace Split’ error is produced after the first cable, but the list only contains a single option for continuing the trace. ![Screen Shot 2020-04-27 at 11 48 36 PM](https://user-images.githubusercontent.com/53161/80445192-a4ac5d00-88e1-11ea-9bed-ab8733d75261.png) I believe this was introduced as part of the changes in #4388. This may be a further regression of that bug. **EDIT:** This only occurs when tracing from the Interface connected to the Rear Port. When tracing through the Front Port, the entire trace completes successfully.
adam added the type: bugstatus: accepted labels 2025-12-29 18:30:12 +01:00
adam closed this issue 2025-12-29 18:30:12 +01:00
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#3617
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?