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

v3.3-beta1: Connection field in interfaces view of device only shows name of connection not device #6677

New Issue
Closed
opened 2025-12-29 19:43:49 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:43:49 +01:00
Owner
Copy Link

Originally created by @themmini on GitHub (Jul 18, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.3-beta1

Python version

3.10

Steps to Reproduce

  1. Open device show connection field in table
  2. Connect interface to another device

image

Expected Behavior

V3.2.6 connection field shows devicename + port assigned
image

Observed Behavior

Connection field only shows portname instead of device_name > portname

Originally created by @themmini on GitHub (Jul 18, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.3-beta1 ### Python version 3.10 ### Steps to Reproduce 1. Open device show connection field in table 2. Connect interface to another device 3. ![image](https://user-images.githubusercontent.com/11536761/179449552-feb09b15-db6d-4c83-a52d-548e98268067.png) ### Expected Behavior V3.2.6 connection field shows devicename + port assigned ![image](https://user-images.githubusercontent.com/11536761/179449600-c7bec937-44cb-4191-afc5-046d25ed45e9.png) ### Observed Behavior Connection field only shows portname instead of device_name > portname
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 19:43:49 +01:00
adam closed this issue 2025-12-29 19:43:49 +01:00
adam commented 2025-12-29 19:43:49 +01:00
Author
Owner
Copy Link

@jaylik commented on GitHub (Jul 20, 2022):

Guess same issue with circuit terminated interfaces which shows "—" as connection on interfaces table.

@jaylik commented on GitHub (Jul 20, 2022): Guess same issue with circuit terminated interfaces which shows "—" as connection on interfaces table.
adam commented 2025-12-29 19:43:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 3, 2022):

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.

@jeremystretch commented on GitHub (Aug 3, 2022): 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.
adam commented 2025-12-29 19:43:50 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Aug 17, 2022):

The issue still exists with Netbox 3.3-beta2. The steps to reproduce are:

  1. Navigate to any device which has at least one cable connection to another device
  2. Select the "Interfaces" tab
  3. Select "Configure Table" to add the "Connection" column, if it's not already present

Example from Netbox v3.2.9:
image

Same example with Netbox v3.3-beta2:
image

EDIT: the "Link Peers" column also suffers the same issue.

(The difference between "Connection" and "Link Peers" is that the former reports the very far end interface across all joined cables, whereas the latter is the connection endpoint of the first cable in the chain, which could go into a frontport on an intermediate patch panel).

@candlerb commented on GitHub (Aug 17, 2022): The issue still exists with Netbox 3.3-beta2. The steps to reproduce are: 1. Navigate to any device which has at least one cable connection to another device 2. Select the "Interfaces" tab 3. Select "Configure Table" to add the "Connection" column, if it's not already present Example from Netbox v3.2.9: ![image](https://user-images.githubusercontent.com/44789/185104263-bf10e0d5-0cc8-431e-9198-265ce1d2d6f0.png) Same example with Netbox v3.3-beta2: ![image](https://user-images.githubusercontent.com/44789/185104706-b21778f6-25a6-4a31-873e-98f1f75f3433.png) EDIT: the "Link Peers" column also suffers the same issue. (The difference between "Connection" and "Link Peers" is that the former reports the very far end interface across all joined cables, whereas the latter is the connection endpoint of the first cable in the chain, which could go into a frontport on an intermediate patch panel).
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 beta 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#6677
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?