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

Connecting Circuit Termination to RearPort Issue #2101

New Issue
Closed
opened 2025-12-29 17:22:20 +01:00 by adam · 7 comments
adam commented 2025-12-29 17:22:20 +01:00
Owner
Copy Link

Originally created by @mmahacek on GitHub (Nov 7, 2018).

Environment

  • Python version: 3.6
  • NetBox version: 2.5 beta 1

Steps to Reproduce

Connect circuit termination to a RearPort of a patch panel. Select patch panel device, select rear_port, select the port instance.

Expected Behavior

A new cable should be created connecting the circuit to the device.

Observed Behavior

I see a new cable is created, but receive the following error:

<class 'django.db.utils.IntegrityError'>

duplicate key value violates unique constraint "dcim_interface__connected_circuittermination_id_key"
DETAIL:  Key (_connected_circuittermination_id)=(126) already exists.

In addition, when looking at the device connected to the corresponding FrontPort, I see a cable connected but there is no far end device. If I trace the connection, it does properly trace to the circuit.

On a separate/slightly related issue, there is no button to disconnect a circuit termination from a specific port. I deleted the cable and was able to reconnect to a new port. However, the device is currently showing that the old port is still connected to the circuit but does not have a cable attached. (see screenshot)
image

Originally created by @mmahacek on GitHub (Nov 7, 2018). ### Environment * Python version: 3.6 * NetBox version: 2.5 beta 1 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce Connect circuit termination to a RearPort of a patch panel. Select patch panel device, select rear_port, select the port instance. <!-- What did you expect to happen? --> ### Expected Behavior A new cable should be created connecting the circuit to the device. <!-- What happened instead? --> ### Observed Behavior I see a new cable is created, but receive the following error: ``` <class 'django.db.utils.IntegrityError'> duplicate key value violates unique constraint "dcim_interface__connected_circuittermination_id_key" DETAIL: Key (_connected_circuittermination_id)=(126) already exists. ``` In addition, when looking at the device connected to the corresponding FrontPort, I see a cable connected but there is no far end device. If I trace the connection, it does properly trace to the circuit. ~~On a separate/slightly related issue, there is no button to disconnect a circuit termination from a specific port. I deleted the cable and was able to reconnect to a new port. However, the device is currently showing that the old port is still connected to the circuit but does not have a cable attached. (see screenshot) ![image](https://user-images.githubusercontent.com/26419758/48162379-c222dc80-e291-11e8-873d-9d7aa908fdf0.png)~~
adam closed this issue 2025-12-29 17:22:20 +01:00
adam commented 2025-12-29 17:22:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 8, 2018):

Connect circuit termination to a RearPort of a patch panel. Select patch panel device, select rear_port, select the port instance.

I'm not able to recreate this. Connecting the cable works as expected. Please see if you can work out the entire workflow needed to reproduce the bug. It likely involves an interface connected at some point in the path.

On a separate/slightly related issue

Needs a separate GitHub issue.

@jeremystretch commented on GitHub (Nov 8, 2018): > Connect circuit termination to a RearPort of a patch panel. Select patch panel device, select rear_port, select the port instance. I'm not able to recreate this. Connecting the cable works as expected. Please see if you can work out the entire workflow needed to reproduce the bug. It likely involves an interface connected at some point in the path. > On a separate/slightly related issue Needs a separate GitHub issue.
adam commented 2025-12-29 17:22:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 8, 2018):

This might be related to #2571

@jeremystretch commented on GitHub (Nov 8, 2018): This might be related to #2571
adam commented 2025-12-29 17:22:21 +01:00
Author
Owner
Copy Link

@mmahacek commented on GitHub (Nov 8, 2018):

Moved second part of original message to https://github.com/digitalocean/netbox/issues/2572

@mmahacek commented on GitHub (Nov 8, 2018): Moved second part of original message to https://github.com/digitalocean/netbox/issues/2572
adam commented 2025-12-29 17:22:21 +01:00
Author
Owner
Copy Link

@mmahacek commented on GitHub (Nov 9, 2018):

I am not able to reproduce the issue now. Not sure if I am following the same steps or if I was trying too many things at once. 🤷‍♂️ I guess this can be closed and I'll see if I can break beta 2 when it comes out.

@mmahacek commented on GitHub (Nov 9, 2018): I am not able to reproduce the issue now. Not sure if I am following the same steps or if I was trying too many things at once. 🤷‍♂️ I guess this can be closed and I'll see if I can break beta 2 when it comes out.
adam commented 2025-12-29 17:22:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 9, 2018):

Thanks. develop-2.5 is under a lot of flux as we iron things out. If it was a bug there's a good chance it's been resolved already anyway.

@jeremystretch commented on GitHub (Nov 9, 2018): Thanks. `develop-2.5` is under a lot of flux as we iron things out. If it was a bug there's a good chance it's been resolved already anyway.
adam commented 2025-12-29 17:22:21 +01:00
Author
Owner
Copy Link

@bsteinert commented on GitHub (Dec 20, 2018):

i run into this issue today, and have a slightly differnt scenario:

i have created a cwdm system with one rear and a lot of front ports. we conneted a circuit (darkfiber in our case) to the rear port.

by adding the first front port, everything looks good.
after adding the second port i get the same error like above.

--> i think there is a 1to1 relationship between circuits and it's connected items. after adding a second front port there is a problem with this object and how it is designed to work.

@bsteinert commented on GitHub (Dec 20, 2018): i run into this issue today, and have a slightly differnt scenario: i have created a cwdm system with one rear and a lot of front ports. we conneted a circuit (darkfiber in our case) to the rear port. by adding the first front port, everything looks good. after adding the second port i get the same error like above. --> i think there is a 1to1 relationship between circuits and it's connected items. after adding a second front port there is a problem with this object and how it is designed to work.
adam commented 2025-12-29 17:22:22 +01:00
Author
Owner
Copy Link

@bsteinert commented on GitHub (Dec 28, 2018):

@jeremystretch should i open a new issue for that, or can you re-open this one for validation?

@bsteinert commented on GitHub (Dec 28, 2018): @jeremystretch should i open a new issue for that, or can you re-open this one for validation?
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
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#2101
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?