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

PATCH requests to cable-terminations do not update the old endpoint #7780

New Issue
Closed
opened 2025-12-29 20:28:07 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:28:07 +01:00
Owner
Copy Link

Originally created by @SheffSix on GitHub (Mar 21, 2023).

NetBox version

v3.4.6

Python version

3.8

Steps to Reproduce

I came across bug #11901 (although I am working with front ports not interfaces), and had the idea of sending the PATCH/PUT to /dcim/cable-terminations/{id} directly instead of the cable.

The results are an imporovement, but still has to problem that the old endpoint still thinks it is connected to the cable.

Steps to reproduce:

  • create three devices
  • Create three rear ports and three front ports, one of each for each device
  • create a cable connection between two of the devices' front ports
  • request an API PATCH HTTP request to change the device and port of b termination to the third device.

Expected Behavior

The cable is moved from port two to port three, and there are no references to the cable on port two

Observed Behavior

Looking at the properties of the cable, it shows that it is connected to ports one and three as expected.

However, from the front port view, port two still reports as being connected to the cable as well as ports one and three.

Originally created by @SheffSix on GitHub (Mar 21, 2023). ### NetBox version v3.4.6 ### Python version 3.8 ### Steps to Reproduce I came across bug #11901 (although I am working with front ports not interfaces), and had the idea of sending the PATCH/PUT to /dcim/cable-terminations/{id} directly instead of the cable. The results are an imporovement, but still has to problem that the old endpoint still thinks it is connected to the cable. Steps to reproduce: - create three devices - Create three rear ports and three front ports, one of each for each device - create a cable connection between two of the devices' front ports - request an API PATCH HTTP request to change the device and port of b termination to the third device. ### Expected Behavior The cable is moved from port two to port three, and there are no references to the cable on port two ### Observed Behavior Looking at the properties of the cable, it shows that it is connected to ports one and three as expected. However, from the front port view, port two still reports as being connected to the cable as well as ports one and three.
adam added the type: bugstatus: acceptedtopic: cablingseverity: medium labels 2025-12-29 20:28:07 +01:00
adam closed this issue 2025-12-29 20:28:07 +01:00
adam commented 2025-12-29 20:28:07 +01:00
Author
Owner
Copy Link

@jozefws commented on GitHub (Mar 24, 2023):

Duplicate of #11901 :)

@jozefws commented on GitHub (Mar 24, 2023): Duplicate of #11901 :)
adam commented 2025-12-29 20:28:07 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 5, 2023):

Duplicate of #11901 :)

It is not.

@jsenecal commented on GitHub (Jul 5, 2023): > Duplicate of #11901 :) It is not.
adam commented 2025-12-29 20:28:08 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 6, 2023):

I repro #11901 but not this one, regardless I think https://github.com/netbox-community/netbox/pull/13337 will fix this as well.

@arthanson commented on GitHub (Sep 6, 2023): I repro #11901 but not this one, regardless I think https://github.com/netbox-community/netbox/pull/13337 will fix this as well.
adam commented 2025-12-29 20:28:08 +01:00
Author
Owner
Copy Link

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

I was not able to reproduce this on v3.6.2 (prior to the merger of PR #13337). It was likely resolved by some other change in a more recent release.

@jeremystretch commented on GitHub (Sep 26, 2023): I was not able to reproduce this on v3.6.2 (prior to the merger of PR #13337). It was likely resolved by some other change in a more recent release.
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 severity: medium 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#7780
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?