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 not working for split cables with multiple endpoints #15948

Closed
arthanson opened this issue May 3, 2024 · 1 comment · Fixed by #15953
Closed

Cable Trace not working for split cables with multiple endpoints #15948

arthanson opened this issue May 3, 2024 · 1 comment · Fixed by #15953
Assignees
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@arthanson
Copy link
Collaborator

arthanson commented May 3, 2024

Deployment Type

NetBox Cloud

NetBox Version

v3.7.7

Python Version

3.8

Steps to Reproduce

  1. Create a Device switch with multiple interfaces
  2. Create a Device that is a patch panel with multiple front ports
  3. Add a single cable that has multiple connections going from the interfaces to the front ports (see screenshot)
  4. View the cable path

cable-add

Expected Behavior

The cable path trace should show the cable that has multiple splits at both ends (see screenshot below)
old-trace

Observed Behavior

The cable path trace is split at the interfaces but is aggregated together to show only a single connection to the first front-port.
new-trace

@arthanson arthanson added type: bug A confirmed report of unexpected behavior in the application severity: medium Results in substantial degraded or broken functionality for specfic workflows status: needs triage This issue is awaiting triage by a maintainer labels May 3, 2024
@jeremystretch jeremystretch removed their assignment May 3, 2024
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: needs triage This issue is awaiting triage by a maintainer labels May 3, 2024
@arthanson
Copy link
Collaborator Author

@Moehritz would you possibly be available to take a look at this? It looks like the changes to draw_fanin from before potentially broke this.

@DanSheps DanSheps removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 3, 2024
@DanSheps DanSheps self-assigned this May 3, 2024
@DanSheps DanSheps added the status: accepted This issue has been accepted for implementation label May 3, 2024
DanSheps added a commit that referenced this issue May 3, 2024
jeremystretch pushed a commit that referenced this issue May 6, 2024
* Preliminary fix for #15948

* Tweaking of line height
jeremystretch pushed a commit that referenced this issue May 6, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants