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

Connection field in dcim/interfaces/ behaves different from versions >= 3.3.x #7007

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

Originally created by @julianstolp on GitHub (Sep 20, 2022).

NetBox version

v3.3.4

Python version

3.8

Steps to Reproduce

  1. Set up Netbox version 3.3.4 and 3.2.9
  2. Create a device1 with 1 interface
  3. Create a device2 with 1 front and rear port
  4. Connect interface from device1 with front port of device 2
  5. Compare the view from /dcim/devices/device1_id/interfaces/

Expected Behavior

The last endpoint should be displayed in the Connection field, regardless of the type (Front, Rear, Interface). According to my understanding the representation is more correct in the versions <=3.3. I could not find any related changelog, issue or discussion on that topic.

Observed Behavior

In Netbox version 3.3 or higher the Connection field is empty.

Originally created by @julianstolp on GitHub (Sep 20, 2022). ### NetBox version v3.3.4 ### Python version 3.8 ### Steps to Reproduce 1. Set up Netbox version 3.3.4 and 3.2.9 2. Create a device1 with 1 interface 3. Create a device2 with 1 front and rear port 4. Connect interface from device1 with front port of device 2 5. Compare the view from /dcim/devices/device1_id/interfaces/ ### Expected Behavior The last endpoint should be displayed in the _Connection_ field, regardless of the type (Front, Rear, Interface). According to my understanding the representation is more correct in the versions <=3.3. I could not find any related changelog, issue or discussion on that topic. ### Observed Behavior In Netbox version 3.3 or higher the _Connection_ field is empty.
adam added the type: bugstatus: duplicate labels 2025-12-29 19:47:48 +01:00
adam closed this issue 2025-12-29 19:47:48 +01:00
adam commented 2025-12-29 19:47:49 +01:00
Author
Owner
Copy Link

@Omripresent commented on GitHub (Sep 20, 2022):

I'm seeing a similar behavior running v3.3.4, while creating a new cable using a custom script

cable = Cable.objects.create(
            a_terminations=[term_a],
            b_terminations=[term_b],
            type=type,
            color=color,
            status=status,
            tenant=tenant,
        )

If I manually edit and save (without any changes) the connection field of term A is populated.
I think there's a problem with the cable path tracing system but I can't point to the exact issue just yet.

@Omripresent commented on GitHub (Sep 20, 2022): I'm seeing a similar behavior running v3.3.4, while creating a new cable using a custom script ```python cable = Cable.objects.create( a_terminations=[term_a], b_terminations=[term_b], type=type, color=color, status=status, tenant=tenant, ) ``` If I manually edit and save (without any changes) the connection field of term A is populated. I think there's a problem with the cable path tracing system but I can't point to the exact issue just yet.
adam commented 2025-12-29 19:47:49 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Sep 23, 2022):

@Omripresent - Your issue is not related to this issue.

Please see my reply here for info on how to properly use the internal API for creating cables.

@kkthxbye-code commented on GitHub (Sep 23, 2022): @Omripresent - Your issue is not related to this issue. [Please see my reply here for info on how to properly use the internal API for creating cables. ](https://github.com/netbox-community/netbox/discussions/10199#discussioncomment-3501406)
adam commented 2025-12-29 19:47:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2022):

Marking this as a duplicate of #10460

@jeremystretch commented on GitHub (Sep 26, 2022): Marking this as a duplicate of #10460
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 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#7007
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?