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

End-to-end connections may not be populated for existing cables when creating rear port connections #3490

New Issue
Closed
opened 2025-12-29 18:29:29 +01:00 by adam · 0 comments
adam commented 2025-12-29 18:29:29 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Mar 19, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.9
  • NetBox version: 2.7.10

Steps to Reproduce

cable_topology

  1. Replicate the topology above using four devices with at leas one interface each, and two patch panels each with two front ports mapped to a single rear port. Do not connect the two panels. (You can paste this script into manage.py nbshell to set up the test topology.)
  2. Verify that all four interfaces show a cable termination but no end-to-end connection to another device.
  3. Connect a cable between the two rear ports.
  4. Check the connection status of each of the four interfaces again.

Expected Behavior

Device1 should show a connection to device 3, and device 2 should show a connection to device 4.

Observed Behavior

Only devices 1 and 3 appear to be connected. The interfaces on devices 3 and 4 do not show an end-to-end connection to one another. However, performing a cable trace from either interface is successful.

Workaround

End-to-end connections are created successfully if the connection between rear ports is created before creating the interface/front port connections.

Originally created by @jeremystretch on GitHub (Mar 19, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.9 * NetBox version: 2.7.10 ### Steps to Reproduce ![cable_topology](https://user-images.githubusercontent.com/13487278/77086881-bfcda800-69d8-11ea-8f58-c66ac4e778c3.png) 1. Replicate the topology above using four devices with at leas one interface each, and two patch panels each with two front ports mapped to a single rear port. Do not connect the two panels. (You can paste [this script](https://github.com/netbox-community/netbox/files/4355589/4388_topology.txt) into `manage.py nbshell` to set up the test topology.) 2. Verify that all four interfaces show a cable termination but no end-to-end connection to another device. 3. Connect a cable between the two rear ports. 4. Check the connection status of each of the four interfaces again. ### Expected Behavior Device1 should show a connection to device 3, and device 2 should show a connection to device 4. ### Observed Behavior Only devices 1 and 3 appear to be connected. The interfaces on devices 3 and 4 do not show an end-to-end connection to one another. However, performing a cable trace from either interface is successful. ### Workaround End-to-end connections are created successfully if the connection between rear ports is created _before_ creating the interface/front port connections.
adam added the type: bugstatus: accepted labels 2025-12-29 18:29:29 +01:00
adam closed this issue 2025-12-29 18:29:29 +01:00
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 status: accepted 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#3490
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?