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

Changes to rear cables does not update the circuit #6185

New Issue
Closed
opened 2025-12-29 19:37:49 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:37:49 +01:00
Owner
Copy Link

Originally created by @Yohannes988 on GitHub (Mar 9, 2022).

NetBox version

3.0.6

Python version

3.8

Steps to Reproduce

You need a circuit with devices with front and rear ports.

  1. Disconnect the rear cable and connect it to a different rear cable
  2. If you now click on circuit you can see that there is no changes done.
  3. Go to one of the front ports in the circuit and disconnect and connect it.
  4. Then you can see that the circuit changes like it should.

Expected Behavior

The circuit should change when I do changes to the rear cables.

Observed Behavior

Circuit did not change even tho changes were made to a rear cable.

Originally created by @Yohannes988 on GitHub (Mar 9, 2022). ### NetBox version 3.0.6 ### Python version 3.8 ### Steps to Reproduce You need a circuit with devices with front and rear ports. 1. Disconnect the rear cable and connect it to a different rear cable 2. If you now click on circuit you can see that there is no changes done. 3. Go to one of the front ports in the circuit and disconnect and connect it. 4. Then you can see that the circuit changes like it should. ### Expected Behavior The circuit should change when I do changes to the rear cables. ### Observed Behavior Circuit did not change even tho changes were made to a rear cable.
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:37:49 +01:00
adam closed this issue 2025-12-29 19:37:49 +01:00
adam commented 2025-12-29 19:37:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 9, 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 (Mar 9, 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.
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: revisions needed 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#6185
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?