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

provider network cable trace UI bug #10064

New Issue
Closed
opened 2025-12-29 21:26:22 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:26:22 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Aug 9, 2024).

Originally assigned to: @jnovinger on GitHub.

Deployment Type

Self-hosted

NetBox Version

v.4.0.8

Python Version

3.12

Steps to Reproduce

Create a device
Create an interface for that device
Create a circuit
Connect the interface to the circuit (Z side)
Create a provider network
Connect the provide network to the circuit (A side)
Do a cable trace for the above circuit 

Easy visual example here: : https://demo.netbox.dev/circuits/circuit-terminations/15/trace/

image

Expected Behavior

When running a cable trace on a circuit that is connected to a provider network, shouldn't the dotted line that connects Termination A actually 'connect' to the Level3 MPLS provider network? Is the large gap there supposed to be there? It's present in the demo site so I'm not sure if this is by design. (pardon my poor mspaint skills)

image

Observed Behavior

image

Originally created by @ghost on GitHub (Aug 9, 2024). Originally assigned to: @jnovinger on GitHub. ### Deployment Type Self-hosted ### NetBox Version v.4.0.8 ### Python Version 3.12 ### Steps to Reproduce Create a device Create an interface for that device Create a circuit Connect the interface to the circuit (Z side) Create a provider network Connect the provide network to the circuit (A side) Do a cable trace for the above circuit  Easy visual example here: : https://demo.netbox.dev/circuits/circuit-terminations/15/trace/ ![image](https://github.com/user-attachments/assets/30579186-6d06-4f83-8bbd-75fd6a993292) ### Expected Behavior When running a cable trace on a circuit that is connected to a provider network, shouldn't the dotted line that connects Termination A actually 'connect' to the Level3 MPLS provider network? Is the large gap there supposed to be there? It's present in the demo site so I'm not sure if this is by design. (pardon my poor mspaint skills) ![image](https://github.com/user-attachments/assets/43479ab4-e3e6-482f-8c12-dc36d52be172) ### Observed Behavior ![image](https://github.com/user-attachments/assets/5b2286d7-7dba-4571-9ec5-c5d4977a949b)
adam added the type: bugstatus: acceptednetboxtopic: cablingseverity: low labels 2025-12-29 21:26:22 +01:00
adam closed this issue 2025-12-29 21:26:22 +01:00
adam commented 2025-12-29 21:26:22 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Aug 9, 2024):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

Please notice in the bug report form: "Additionally, do not rely on the demo instance for reproducing suspected bugs, as its data is prone to modification or deletion at any time."

@arthanson commented on GitHub (Aug 9, 2024): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports. Please notice in the bug report form: "Additionally, **do not rely on the demo instance** for reproducing suspected bugs, as its data is prone to modification or deletion at any time."
adam commented 2025-12-29 21:26:23 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 9, 2024):

apologies, I've updated the report to include the exact steps to generate the visual pictures included.

@ghost commented on GitHub (Aug 9, 2024): apologies, I've updated the report to include the exact steps to generate the visual pictures included.
adam commented 2025-12-29 21:26:23 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 24, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 24, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
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 netbox severity: low status: accepted topic: cabling 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#10064
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?