Cable not tracing when creating frontports after connecting rearport

[PaulR282]

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.

[jeremystretch]

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.

[PaulR282]

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.

[DeemGit]

@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.

[PaulR282]

@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.

[DeemGit]

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

[jeremystretch]

@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.

[PaulR282]

@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]

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"

[jeremystretch]

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.

[PaulR282]

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