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

Cached properties in CableTermination not updated #6691

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

Originally created by @mzbroch on GitHub (Jul 20, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.3-beta

Python version

3.8

Steps to Reproduce

  1. Populate NetBox with the data mandatory for adding two different Devices: Manufacturer, Device Type, Site (site1), ...
  2. Create two devices ("device1", "device2"), each having set of interfaces ("intf[1-5]") - assign devices to site1.
  3. Connect intf1 of device1 to intf1 of device2
  4. Navigate to cable list view (connections), check out the assigned site - expected site1
  5. Create a new site (site2)
  6. Edit device1 and device2 - change site to site2
  7. Navigate to cable list view (connections), check out the assigned site - expected site2

Expected Behavior

Respective cable between intf1 and intf1 (in a cables list view (connections)) shows site2 as it replaced site1

Observed Behavior

Respective cable between intf1 and intf1 (in a cables list view (connections)) shows cached (invalid) site site1

Originally created by @mzbroch on GitHub (Jul 20, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.3-beta ### Python version 3.8 ### Steps to Reproduce 1. Populate NetBox with the data mandatory for adding two different Devices: Manufacturer, Device Type, Site (`site1`), ... 2. Create two devices ("device1", "device2"), each having set of interfaces ("intf[1-5]") - assign devices to `site1`. 3. Connect `intf1` of `device1` to `intf1` of `device2` 4. Navigate to cable list view (connections), check out the assigned site - expected `site1` 5. Create a new site (`site2`) 6. Edit `device1` and `device2` - change site to `site2` 7. Navigate to cable list view (connections), check out the assigned site - expected `site2` ### Expected Behavior Respective cable between `intf1` and `intf1` (in a cables list view (connections)) shows `site2` as it replaced `site1` ### Observed Behavior Respective cable between `intf1` and `intf1` (in a cables list view (connections)) shows cached (invalid) site `site1`
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 19:44:02 +01:00
adam closed this issue 2025-12-29 19:44:02 +01:00
adam commented 2025-12-29 19:44:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 20, 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 (Jul 20, 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.
adam commented 2025-12-29 19:44:03 +01:00
Author
Owner
Copy Link

@mzbroch commented on GitHub (Jul 20, 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.

Updated the report.

@mzbroch commented on GitHub (Jul 20, 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. Updated the report.
adam commented 2025-12-29 19:44:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 25, 2022):

This looks like a typical denormalization issue, where we just need the cached values up to date. We could handle this with dedicated signal receivers as we do elsehwere in NetBox, but it's probably worth investigating more robust solutions.

@jeremystretch commented on GitHub (Jul 25, 2022): This looks like a typical denormalization issue, where we just need the cached values up to date. We could handle this with dedicated signal receivers as we do elsehwere in NetBox, but it's probably worth investigating more robust solutions.
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 beta status: accepted 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#6691
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?