Circuit selection from a patchpanel not working #2325

Closed
opened 2025-12-29 17:24:50 +01:00 by adam · 9 comments
Owner

Originally created by @lcioltan on GitHub (Jan 30, 2019).

Environment

  • Python version: Python 3.5.3
  • NetBox version: Netbox 2.5.4

Steps to Reproduce

  1. Use a version of a patchpanel with interfaces (let us name it "Patchpanel-A").
  2. The rear port (Port-1) is connected to a distant patchpanel ("Patchpanel-B") via a carrier circuit ("Carrier-1"). The "Carrier-1" circuit has been defined in Netbox and it's listed under Circuits.
  3. On the "Patchpanel-A" overview, under column "Connection", the distant "Patchpanel-B" is outputted and below it, with small letters, this circuit that connects the two panels (via "Carrier-1").
  4. When you click on the circuit "Carrier-1", instead of being redirected to the circuit details,
    you land once again on the "Patchpanel-A"

Note: the problem doesn't appear with the front/rear ports patchpanels.

Expected Behavior

I expect to be redirected to the "Carrier-1" circuit.

Observed Behavior

I land on the exact same patchpanel (acts as a "refresh")

Originally created by @lcioltan on GitHub (Jan 30, 2019). ### Environment * Python version: Python 3.5.3 * NetBox version: Netbox 2.5.4 ### Steps to Reproduce 1. Use a version of a patchpanel with interfaces (let us name it "Patchpanel-A"). 2. The rear port (Port-1) is connected to a distant patchpanel ("Patchpanel-B") via a carrier circuit ("Carrier-1"). The "Carrier-1" circuit has been defined in Netbox and it's listed under Circuits. 3. On the "Patchpanel-A" overview, under column "Connection", the distant "Patchpanel-B" is outputted and below it, with small letters, this circuit that connects the two panels (via "Carrier-1"). 4. When you click on the circuit "Carrier-1", instead of being redirected to the circuit details, you land once again on the "Patchpanel-A" Note: the problem doesn't appear with the front/rear ports patchpanels. ### Expected Behavior I expect to be redirected to the "Carrier-1" circuit. ### Observed Behavior I land on the exact same patchpanel (acts as a "refresh")
adam closed this issue 2025-12-29 17:24:50 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jan 30, 2019):

Just use the "old" version of a patchpanel (with interfaces)

There is no "old" version of patch panels. Support for patch panels was introduced in v2.5. Please clarify what you mean.

@jeremystretch commented on GitHub (Jan 30, 2019): > Just use the "old" version of a patchpanel (with interfaces) There is no "old" version of patch panels. Support for patch panels was introduced in v2.5. Please clarify what you mean.
Author
Owner

@lcioltan commented on GitHub (Jan 30, 2019):

Hi Jeremy,

I meant the patchpanel with interfaces (not with front/rear ports).

@lcioltan commented on GitHub (Jan 30, 2019): Hi Jeremy, I meant the patchpanel with interfaces (not with front/rear ports).
Author
Owner

@jeremystretch commented on GitHub (Jan 30, 2019):

Please edit your issue to include the exact steps that someone else can take to recreate the issue you're describing.

@jeremystretch commented on GitHub (Jan 30, 2019): Please edit your issue to include the exact steps that someone else can take to recreate the issue you're describing.
Author
Owner

@lcioltan commented on GitHub (Jan 30, 2019):

I just updated the description (Steps to reproduce).

@lcioltan commented on GitHub (Jan 30, 2019): I just updated the description (Steps to reproduce).
Author
Owner

@lcioltan commented on GitHub (Feb 8, 2019):

circuit selection from a patchpanel not working

@lcioltan commented on GitHub (Feb 8, 2019): ![circuit selection from a patchpanel not working](https://user-images.githubusercontent.com/47182087/52486679-09d04180-2bbc-11e9-9b46-c40e92dd7e1d.png)
Author
Owner

@lcioltan commented on GitHub (Feb 8, 2019):

Hi Jeremy,

I've attached a picture to better highlight the issue. If you need extra information, just let me know.

@lcioltan commented on GitHub (Feb 8, 2019): Hi Jeremy, I've attached a picture to better highlight the issue. If you need extra information, just let me know.
Author
Owner

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

I believe this was addressed under #2844 and will be fixed in v2.5.6. If you still have the issue on the new release, please ask for this to be reopened.

@jeremystretch commented on GitHub (Feb 8, 2019): I believe this was addressed under #2844 and will be fixed in v2.5.6. If you still have the issue on the new release, please ask for this to be reopened.
Author
Owner

@lcioltan commented on GitHub (Feb 18, 2019):

Hi Jeremy,

the issue persist after the v2.5.6 release. Can we re-open this ticket or should I create a new one?

Kind regards,
Lucian

@lcioltan commented on GitHub (Feb 18, 2019): Hi Jeremy, the issue persist after the v2.5.6 release. Can we re-open this ticket or should I create a new one? Kind regards, Lucian
Author
Owner

@tvberlin commented on GitHub (Feb 21, 2019):

@jeremystretch this is duplicated (and fixed now in 2.5.7) by #2914 and can now be closed, thanks.
@lcioltan FYI

@tvberlin commented on GitHub (Feb 21, 2019): @jeremystretch this is duplicated (and fixed now in 2.5.7) by #2914 and can now be closed, thanks. @lcioltan FYI
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2325