Cable Trace not working in both directions

[mat-vc]

Deployment Type

Self-hosted

NetBox Version

4.0.6

Python Version

3.11

Steps to Reproduce

Create 1 patch-device with 1 front and 1 rear port.

Create 2 devices with 1 interface on each device.
Connect both devices to their corresponding rear/front port.

Press the "trace cable" button to produce a result.

Expected Behavior

I am expecting both trace directions to show the same output. This is not the case.

I'm using a fresh docker environment to test this issue. I've observed this on another environment too.

Observed Behavior

The trace from both sides is giving a different output.
One shows the expected (full) result. The other shows only 1 out of 2 connected patch-cables.

[arthanson]

@mat-vc Can you please check the steps to reproduce and maybe give a more in-depth step by step - I tried a scenario like you listed but can see the trace from both sides (see below):

[github-actions]

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

[dfex]

I am seeing this issue intermittently as well. Netbox 4.0.7 via netbox-docker.

I have a slightly more complex scenario where I have modelled two FOBOT Devices with Front and Rear ports, with "Switch" Device Interfaces connected to the FOBOT Front Ports and the FOBOT Rear Ports connected to each other:

Device [SWITCH1] -> interface -> Cable -> front-port -> device [FOBOT1] -> rear-port -> Cable -> rear-port -> device [FOBOT2] -> front-port -> Cable -> interface -> Device [SWITCH2]

Earlier when I was looking at the SWITCH1 interface list, it showed the nominated interface connected through to the far-end SWITCH2 interface (solving all the intermediate passive device connectivity), however looking at the SWITCH2 interface, it only showed the CableName and the Connected column was blank. Running Trace showed the same one-way results as @mat-vc was seeing (eg: a split after FOBOT2) - and this is when I searched on the cause of the split error message and found this GitHub Issue.

Docker (and thus netbox) has restarted during this time as my laptop was closed.

However, just now, I re-created @arthanson 's test scenario above on separate test devices with a simple back-to-back device in the middle, and trace worked in both directions for that scenario.

Now all of a sudden I can also see a bidirectional connection on my more complex scenario as well! So I'm not sure if that was the restart or something else that is causing it to trace both ways correctly.

[mat-vc]

My apologies for my late reply.

I have just deployed netbox-docker (4.0.8) on another fresh docker environment.
So far, I've observed this issue on versions v3.7.4, 4.0.6, 4.0.7 and 4.0.8.

After testing a few cables it happened again. It only happens sometimes, I can't quiet put my finger on what specifically triggers it, to thow this error...

A few screenshots: Cables 1-2 and 3-4 are OK. Cable 5+6 throw the error only in 1 trace direction.

Trace directions:

Cable 1+2 (works)

Patchpanel used for cable 1-4. Positions are always 1. On both front & rear ports.

Patchpanel used for cable 5-6. Positions are dynamic but do match on front&rear for this device

Could the device template's position have anything to do with it?