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

Cable not tracing when creating frontports after connecting rearport #6920

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

Originally created by @PaulR282 on GitHub (Sep 1, 2022).

NetBox version

v3.3.1

Python version

3.10

Steps to Reproduce

  1. Create a device and add a rearport
  2. Connect the rearport to e.g. another rearport
  3. add frontports to the rearports
  4. create everything needed to trace through the rearport of 1. (if -> fp -> rp (from 1.) -> rp -> fp -> if)
  5. trace the route
  6. click on a rearport in the trace view

Expected Behavior

Complete cable paths should be shown.

Observed Behavior

One Incomplete Path in Related Paths that won't trace the whole route.

Originally created by @PaulR282 on GitHub (Sep 1, 2022). ### NetBox version v3.3.1 ### Python version 3.10 ### Steps to Reproduce 1. Create a device and add a rearport 3. Connect the rearport to e.g. another rearport 4. add frontports to the rearports 5. create everything needed to trace through the rearport of 1. (if -> fp -> rp (from 1.) -> rp -> fp -> if) 6. trace the route 7. click on a rearport in the trace view ### Expected Behavior Complete cable paths should be shown. ### Observed Behavior One Incomplete Path in Related Paths that won't trace the whole route.
adam added the type: bug label 2025-12-29 19:46:42 +01:00
adam closed this issue 2025-12-29 19:46:42 +01:00
adam commented 2025-12-29 19:46:42 +01:00
Author
Owner
Copy Link

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

I'm afraid this isn't enough detail to reproduce. Please specify exactly what you're doing at each step along the way, so that someone else can attempt to reproduce the reported issue.

@jeremystretch commented on GitHub (Sep 1, 2022): I'm afraid this isn't enough detail to reproduce. Please specify exactly what you're doing at each step along the way, so that someone else can attempt to reproduce the reported issue.
adam commented 2025-12-29 19:46:43 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Sep 2, 2022):

So the key is to create the frontports after the rearport is connected. If you then go in the rearport and click on the trace button next to the cable at the "Connection" field, one trace is incomplete.

Let me know if you want more detailed instructions.

@PaulR282 commented on GitHub (Sep 2, 2022): So the key is to create the frontports after the rearport is connected. If you then go in the rearport and click on the trace button next to the cable at the "Connection" field, one trace is incomplete. Let me know if you want more detailed instructions.
adam commented 2025-12-29 19:46:43 +01:00
Author
Owner
Copy Link

@DeemGit commented on GitHub (Sep 2, 2022):

@jeremystretch

I recorded a video demonstrating @PaulR282 explanation.
https://youtu.be/4DUA-YFW_Ow

So, in short: Create 2 patch panels, connect 2 rear ports. Create 2 devices (ex routers). connect 1 interface to 2 front ports in patch panel for both of them. click "trace" and get an exception.

@DeemGit commented on GitHub (Sep 2, 2022): @jeremystretch I recorded a video demonstrating @PaulR282 explanation. [https://youtu.be/4DUA-YFW_Ow](https://youtu.be/4DUA-YFW_Ow) So, in short: Create 2 patch panels, connect 2 rear ports. Create 2 devices (ex routers). connect 1 interface to 2 front ports in patch panel for both of them. click "trace" and get an exception.
adam commented 2025-12-29 19:46:43 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Sep 2, 2022):

@DeemGit

Thanks for the video, but this is not what I meant. As I said, the problem occurs when creating a rearport, connecting that rearport, and then creating the frontports and connecting them.

@PaulR282 commented on GitHub (Sep 2, 2022): @DeemGit Thanks for the video, but this is not what I meant. As I said, the problem occurs when creating a rearport, connecting that rearport, and then creating the frontports and connecting them.
adam commented 2025-12-29 19:46:43 +01:00
Author
Owner
Copy Link

@DeemGit commented on GitHub (Sep 2, 2022):

@PaulR282
That was shown in the first part of video. Anyway some kind of a bug exists.

@DeemGit commented on GitHub (Sep 2, 2022): @PaulR282 That was shown in the first part of video. Anyway some kind of a bug exists.
adam commented 2025-12-29 19:46:44 +01:00
Author
Owner
Copy Link

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

@DeemGit thanks for taking the time to record the video. The bug you encountered has been captured under #10217 and is resolved in the upcoming release.

@PaulR282 I'm afraid I'm still not able to reproduce the reported behavior under the current develop branch. It's possible that it may have already been resolved under another bug.

@jeremystretch commented on GitHub (Sep 2, 2022): @DeemGit thanks for taking the time to record the video. The bug you encountered has been captured under #10217 and is resolved in the upcoming release. @PaulR282 I'm afraid I'm still not able to reproduce the reported behavior under the current `develop` branch. It's possible that it may have already been resolved under another bug.
adam commented 2025-12-29 19:46:44 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Sep 5, 2022):

@jeremystretch I tried to reproduce the problem in the latest version, but it looks like it has been resolved. However, there is now another problem but I'm going to make a new BR for this one.

@PaulR282 commented on GitHub (Sep 5, 2022): @jeremystretch I tried to reproduce the problem in the latest version, but it looks like it has been resolved. However, there is now another problem but I'm going to make a new BR for this one.
adam commented 2025-12-29 19:46:45 +01:00
Author
Owner
Copy Link

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

I need to correct myself, the issue has not been resolved. I reproduced it in the latest v3.3.2-dev version. Here are detailed steps to reproduce:

  1. Create 2 Switche (or some sort of device with interfaces)
  2. Create 2 devices that will function as patchpanel (these need to be empty, so no rear or frontports from the device type)
  3. Create a rearport in both patchpanel
  4. Connect the rearports
  5. Create at least 1 frontport in both patchpanel
  6. Connect each frontport to a switch so you get the following path:
    Interface Switch 1 -> Frontport Patchpanel 1 -> RP Patchpanel 1 -> RP Patchpanel 2 -> FP Patchpanel 2 -> Interface Switch 2
  7. Go to one of the rearports of the patchpanel
  8. Click on "Trace" next to the cable ID
    2 complete traces should be shown (from one interface to another and vise versa) but 1 trace is incomplete. You can also see it in one of the connected interfaces, where the Connection Path Status shows "Not Reachable"
@PaulR282 commented on GitHub (Sep 6, 2022): I need to correct myself, the issue has not been resolved. I reproduced it in the latest v3.3.2-dev version. Here are detailed steps to reproduce: 1. Create 2 Switche (or some sort of device with interfaces) 2. Create 2 devices that will function as patchpanel (these need to be empty, so no rear or frontports from the device type) 3. Create a rearport in both patchpanel 4. Connect the rearports 5. Create at least 1 frontport in both patchpanel 6. Connect each frontport to a switch so you get the following path: Interface Switch 1 -> Frontport Patchpanel 1 -> RP Patchpanel 1 -> RP Patchpanel 2 -> FP Patchpanel 2 -> Interface Switch 2 7. Go to one of the rearports of the patchpanel 8. Click on "Trace" next to the cable ID 2 complete traces should be shown (from one interface to another and vise versa) but 1 trace is incomplete. You can also see it in one of the connected interfaces, where the Connection Path Status shows "Not Reachable"
adam commented 2025-12-29 19:46:45 +01:00
Author
Owner
Copy Link

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

I reproduced it in the latest v3.3.2-dev version.

This could indicate any point along the development of v3.3.2. Please try the final v3.3.2 release now that it's available.

@jeremystretch commented on GitHub (Sep 6, 2022): > I reproduced it in the latest v3.3.2-dev version. This could indicate any point along the development of v3.3.2. Please try the final v3.3.2 release now that it's available.
adam commented 2025-12-29 19:46:45 +01:00
Author
Owner
Copy Link

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

I reproduced it in the latest v3.3.2-dev version.

This could indicate any point along the development of v3.3.2. Please try the final v3.3.2 release now that it's available.

It's the same in v3.3.2

@PaulR282 commented on GitHub (Sep 6, 2022): > > I reproduced it in the latest v3.3.2-dev version. > > This could indicate any point along the development of v3.3.2. Please try the final v3.3.2 release now that it's available. It's the same in v3.3.2
adam commented 2025-12-29 19:46:45 +01:00
Author
Owner
Copy Link

@jdp-minpcdk commented on GitHub (Sep 15, 2022):

In v3.3.2 Cable not tracing, I create a circuits termination connected to front port(patch panel), but working when I connect to a Interface port.

@jdp-minpcdk commented on GitHub (Sep 15, 2022): In v3.3.2 Cable not tracing, I create a circuits termination connected to front port(patch panel), but working when I connect to a Interface port.
adam commented 2025-12-29 19:46:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 17, 2022):

I'm not able to reproduce this on v3.3.8 using the steps provided above: Both end-to-end paths are created successfully as expected.

Screenshot 2022-11-17 at 15-46-45 Cable Trace for Rear Port RP1 NetBox

I'm going to close this issue as it has likely been resolved by some other change. If anyone is able to reproduce the error on the current release, please open a new issue with complete reproduction steps.

@jeremystretch commented on GitHub (Nov 17, 2022): I'm not able to reproduce this on v3.3.8 using the steps [provided above](https://github.com/netbox-community/netbox/issues/10237#issuecomment-1237915215): Both end-to-end paths are created successfully as expected. ![Screenshot 2022-11-17 at 15-46-45 Cable Trace for Rear Port RP1 NetBox](https://user-images.githubusercontent.com/13487278/202556351-524eeee0-c777-41dd-b4c7-ed7cd496b88f.png) I'm going to close this issue as it has likely been resolved by some other change. If anyone is able to reproduce the error on the current release, please open a **new** issue with complete reproduction steps.
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 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#6920
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?