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

full trace (interface to interface) not available if using circuits between sites #4515

New Issue
Closed
opened 2025-12-29 18:36:53 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:36:53 +01:00
Owner
Copy Link

Originally created by @Gheorghita on GitHub (Jan 29, 2021).

Environment

  • Python version: 3.6.8
  • NetBox version: v2.10.4

Steps to Reproduce

  1. Create 3 sites in different regions with devices
  2. create 2 circuits
  3. connect one device from site A to Site C via Site B
    multipleSites

Expected Behavior

Trace from interface 1 (site A) to interface 2 (site C)
1-n-splice-noCircuite-Cable Trace for Interface gi25 - NetBox

Observed Behavior

trace breaks at the first circuit.
1-n-splice-Circuite-Cable Trace for Interface gi25 - NetBox

Works as expected if I don't use circuits and directly connect ports from different sites. (trace from the first picture is the result)

Originally created by @Gheorghita on GitHub (Jan 29, 2021). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reporting reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions 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.6.8 * NetBox version: v2.10.4 <!-- 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. Create 3 sites in different regions with devices 2. create 2 circuits 3. connect one device from site A to Site C via Site B ![multipleSites](https://user-images.githubusercontent.com/9327352/106280768-03bf4980-6247-11eb-9ef6-ea6d9f704599.png) <!-- What did you expect to happen? --> ### Expected Behavior Trace from interface 1 (site A) to interface 2 (site C) ![1-n-splice-noCircuite-Cable Trace for Interface gi25 - NetBox](https://user-images.githubusercontent.com/9327352/106279654-6adbfe80-6245-11eb-8524-ac163e3e4216.png) <!-- What happened instead? --> ### Observed Behavior trace breaks at the first circuit. ![1-n-splice-Circuite-Cable Trace for Interface gi25 - NetBox](https://user-images.githubusercontent.com/9327352/106280093-1e44f300-6246-11eb-8f61-cf3f0f8078de.png) Works as expected if I don't use circuits and directly connect ports from different sites. (trace from the first picture is the result)
adam closed this issue 2025-12-29 18:36:53 +01:00
adam commented 2025-12-29 18:36:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 29, 2021):

This is expected behavior and is specifically called out in the v2.10 release notes: Circuits are considered endpoints of the cable path. This change was made to fix several bugs which had plagued the cable tracing logic for a long time.

@jeremystretch commented on GitHub (Jan 29, 2021): This is expected behavior and is specifically called out in the [v2.10 release notes](https://netbox.readthedocs.io/en/stable/release-notes/version-2.10/#new-features): Circuits are considered endpoints of the cable path. This change was made to fix several bugs which had plagued the cable tracing logic for a long time.
adam commented 2025-12-29 18:36:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2021):

FYI I've opened #6071 to address this as a feature request.

@jeremystretch commented on GitHub (Mar 30, 2021): FYI I've opened #6071 to address this as a feature request.
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#4515
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?