Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cable trace does not follow circuits #2691

Closed
thoms27 opened this issue Dec 14, 2018 · 0 comments
Closed

Cable trace does not follow circuits #2691

thoms27 opened this issue Dec 14, 2018 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@thoms27
Copy link

thoms27 commented Dec 14, 2018

Environment

  • Python version: 2.7.5
  • NetBox version: 2.5.0

Steps to Reproduce

  • Create a device Device-A with an interface A

  • Create a device Device-B witch an inteface B

  • Create a device PatchPanel-A with a Rear Port A and a Front Port A

  • Create a device PatchPanel-B with a Rear Port B and a Front Port B

  • Create a circuit Circuit-AB

  • Connect Device-A interface A to PatchPanel-A Front Port A

  • Connect Device-B interface B to PatchPanel-B Front Port B

  • Connect Circuit-AB A-Side to PatchPanel-A Rear Port A

  • Connect Circuit-AB Z-Side to PatchPanel-B Rear Port B

Expected Behavior

When you click on trace on the Device-A interface A, we should see the complete path to Device-B interface B.
If I'm not insert a circuit, I see the complete path (Connecting the Rear port of the PatchPanel A & B).

Observed Behavior

I just see the half trace to Circuit-AB A-Side

Below the picture :

Device-A
image

Device-B
image

Is it normal ?

Thanks for your help.

Regards,

ThomasV

@jeremystretch jeremystretch changed the title Tracing half path with Circuit Cable trace does not follow circuits Dec 19, 2018
@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation labels Dec 19, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants