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

Caching issue: Renaming a slave device is not visible on the parent device #2771

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

Originally created by @phurrelmann on GitHub (Aug 1, 2019).

Environment

  • Python version: 3.5.3
  • NetBox version: 2.6.1

Steps to Reproduce

  1. Rename a child device that is assigned to a parent
  2. Go back to the parent
  3. The parent still shows the old name of the child
  4. Go to the child and verify that it really was renamed
  5. After the cache expired the new name is visble on the parent, too

Expected Behavior

The child device is immediatly shown with its new name (when looked from the parent)

Observed Behavior

The child device is still shown with its old name (when looked from the parent) until the cache expires (default 900s).

Originally created by @phurrelmann on GitHub (Aug 1, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5.3 * NetBox version: 2.6.1 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Rename a child device that is assigned to a parent 2. Go back to the parent 3. The parent still shows the old name of the child 4. Go to the child and verify that it really was renamed 5. After the cache expired the new name is visble on the parent, too <!-- What did you expect to happen? --> ### Expected Behavior The child device is immediatly shown with its new name (when looked from the parent) <!-- What happened instead? --> ### Observed Behavior The child device is still shown with its old name (when looked from the parent) until the cache expires (default 900s).
adam closed this issue 2025-12-29 18:22:01 +01:00
adam commented 2025-12-29 18:22:02 +01:00
Author
Owner
Copy Link

@phurrelmann commented on GitHub (Aug 1, 2019):

The same happens for the device status. A change in a child's device status is not seen on the parent until the cache expires.

@phurrelmann commented on GitHub (Aug 1, 2019): The same happens for the device status. A change in a child's device status is not seen on the parent until the cache expires.
adam commented 2025-12-29 18:22:02 +01:00
Author
Owner
Copy Link

@Solvik commented on GitHub (Aug 5, 2019):

I've stumpled upon this case and others
From what I can see, the cache invalidation upon modification isn't working correctly.. it requires to wait for the cache expiration

@Solvik commented on GitHub (Aug 5, 2019): I've stumpled upon this case and others From what I can see, the cache invalidation upon modification isn't working correctly.. it requires to wait for the cache expiration
adam commented 2025-12-29 18:22:02 +01:00
Author
Owner
Copy Link

@netaviator commented on GitHub (Aug 9, 2019):

Same problem here. The list on the parent is not rehresehd if the name of the child device is updated.

@netaviator commented on GitHub (Aug 9, 2019): Same problem here. The list on the parent is not rehresehd if the name of the child device is updated.
adam commented 2025-12-29 18:22:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 15, 2019):

Rolled into #3428

@jeremystretch commented on GitHub (Aug 15, 2019): Rolled into #3428
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#2771
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?