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

Device web view : rear port connection view refers to its own device #2374

New Issue
Closed
opened 2025-12-29 17:25:28 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:25:28 +01:00
Owner
Copy Link

Originally created by @louis-6wind on GitHub (Feb 13, 2019).

Environment

  • Python version: 3.6.6
  • NetBox version: 2.5.5

Steps to Reproduce

  1. Connect a cable between rear port of two devices

Observed Behavior

When browsing on both devices with http://XXX/dcim/devices/, the rear port view of both devices refers to the same device name and url in the connection field. That means : on one device, the data in connection field is correct and refers to the correct remote device and on the other one, the output refers to the itself.

However, cable terminations are correct in http://XXX/dcim/cables/

Expected Behavior

Rear port connection field should always refers to the other termination device not to its device.

Originally created by @louis-6wind on GitHub (Feb 13, 2019). ### Environment * Python version: 3.6.6 * NetBox version: 2.5.5 ### Steps to Reproduce 1. Connect a cable between rear port of two devices ### Observed Behavior When browsing on both devices with http://XXX/dcim/devices/<id>, the rear port view of both devices refers to the same device name and url in the connection field. That means : on one device, the data in connection field is correct and refers to the correct remote device and on the other one, the output refers to the itself. However, cable terminations are correct in http://XXX/dcim/cables/<id> ### Expected Behavior Rear port connection field should always refers to the other termination device not to its device.
adam added the status: duplicate label 2025-12-29 17:25:28 +01:00
adam closed this issue 2025-12-29 17:25:28 +01:00
adam commented 2025-12-29 17:25:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 13, 2019):

Already addressed under #2844 and will be fixed in v2.5.6.

@jeremystretch commented on GitHub (Feb 13, 2019): Already addressed under #2844 and will be fixed in v2.5.6.
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: duplicate
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#2374
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?