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

No Cable Trace without Interface #5717

New Issue
Closed
opened 2025-12-29 19:31:47 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:31:47 +01:00
Owner
Copy Link

Originally created by @PaulR282 on GitHub (Nov 30, 2021).

NetBox version

v3.0.9

Python version

3.7

Steps to Reproduce

  1. Create Rack
  2. Add patchpanel device with front and rearport
  3. Add second patchpanel in same or other rack
  4. Connect rearports
  5. Connect a frontport to something that is not a interface (e.g. frontport of same patchpanel)
    (connect as many device in series as you want (frontport device 1 -> rearport device 1, rearport device 1 -> rearport device 2, rearport device 2 -> frontport device 2 ...and so on...)
  6. Click cable trace on the cable

Expected Behavior

The cable trace is shown

Observed Behavior

'No paths found'

Originally created by @PaulR282 on GitHub (Nov 30, 2021). ### NetBox version v3.0.9 ### Python version 3.7 ### Steps to Reproduce 1. Create Rack 2. Add patchpanel device with front and rearport 3. Add second patchpanel in same or other rack 4. Connect rearports 5. Connect a frontport to something that is not a interface (e.g. frontport of same patchpanel) (connect as many device in series as you want (frontport device 1 -> rearport device 1, rearport device 1 -> rearport device 2, rearport device 2 -> frontport device 2 ...and so on...) 6. Click cable trace on the cable ### Expected Behavior The cable trace is shown ### Observed Behavior 'No paths found'
adam closed this issue 2025-12-29 19:31:47 +01:00
adam commented 2025-12-29 19:31:48 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 30, 2021):

Hello,

This is not a bug, it is in fact an intended consequence of the new way cable traces are done.

@DanSheps commented on GitHub (Nov 30, 2021): Hello, This is not a bug, it is in fact an intended consequence of the new way cable traces are done.
adam commented 2025-12-29 19:31:48 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Nov 30, 2021):

What is the benefit of this 'feature'?

@PaulR282 commented on GitHub (Nov 30, 2021): What is the benefit of this 'feature'?
adam commented 2025-12-29 19:31:48 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 30, 2021):

What is the benefit of this 'feature'?

This isn't a "feature", this is the way cable paths are done. There must be a start interface/circuit for the path to be considered valid

@DanSheps commented on GitHub (Nov 30, 2021): > What is the benefit of this 'feature'? This isn't a "feature", this is the way cable paths are done. There **must** be a start interface/circuit for the path to be considered valid
adam commented 2025-12-29 19:31:49 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Nov 30, 2021):

So it can't be changed or patched, that it works without an interface?

@PaulR282 commented on GitHub (Nov 30, 2021): So it can't be changed or patched, that it works without an interface?
adam commented 2025-12-29 19:31:49 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 30, 2021):

Yes it can, but it needs to be developed as a feature and not as a bug.

At this point, because you don't seem to understand the process, I am first going to direct you to review the Contributing guidelines as well as the wiki to review the Getting Involed section and the Issue intake policy.

Once done, please open this as a proper feature request using the provided form for feature requests.

@DanSheps commented on GitHub (Nov 30, 2021): Yes it can, but it needs to be developed as a feature and not as a bug. At this point, because you don't seem to understand the process, I am first going to direct you to review the [Contributing guidelines](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md) as well as the wiki to review the [Getting Involed](https://github.com/netbox-community/netbox/wiki/Getting-Involved) section and the [Issue intake policy](https://github.com/netbox-community/netbox/wiki/Issue-Intake-Policy). Once done, please open this as a proper feature request using the provided form for feature requests.
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#5717
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?