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

Data cache not being invalidated after move to 2.11.1 #4845

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

Originally created by @karrots on GitHub (Apr 29, 2021).

NetBox version

v2.11.1

Python version

3.8

Steps to Reproduce

  1. Upgrade from 2.10.x to 2.11.x
  2. Move a location from one site to another.
  3. Open the old site and view statistics. Rack counts and other item counts will remain in the old site.
  4. Click on a statistic to view the filtered list. The filter will show the old site name. The data in the list will show the new site name.
  5. Wait for cache to time out. Data will now be in sync.

Expected Behavior

The cache should be invalidated immediately due to data change.

Observed Behavior

Cache not being invalidated.

Originally created by @karrots on GitHub (Apr 29, 2021). ### NetBox version v2.11.1 ### Python version 3.8 ### Steps to Reproduce 1. Upgrade from 2.10.x to 2.11.x 2. Move a location from one site to another. 3. Open the old site and view statistics. Rack counts and other item counts will remain in the old site. 4. Click on a statistic to view the filtered list. The filter will show the old site name. The data in the list will show the new site name. 5. Wait for cache to time out. Data will now be in sync. ### Expected Behavior The cache should be invalidated immediately due to data change. ### Observed Behavior Cache not being invalidated.
adam added the type: bug label 2025-12-29 19:21:12 +01:00
adam closed this issue 2025-12-29 19:21:12 +01:00
adam commented 2025-12-29 19:21:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 29, 2021):

I'm not able to reproduce the reported behavior following the steps provided. Please elaborate on your steps above to start with the creation of each object, and detailing exactly what actions you are taking at each step.

@jeremystretch commented on GitHub (Apr 29, 2021): I'm not able to reproduce the reported behavior following the steps provided. Please elaborate on your steps above to start with the creation of each object, and detailing _exactly_ what actions you are taking at each step.
adam commented 2025-12-29 19:21:13 +01:00
Author
Owner
Copy Link

@karrots commented on GitHub (Apr 29, 2021):

Objects existed before the migration to 2.11

Objects moved were rack groups now locations.

I moved the location to a different site as part of a consolidation of
sites. The individual racks assigned to that location showed the new site
in their pages. When opening a rack it showed the updated site. When
looking at the old site stats page it still listed 28 racks when it should
have listed 0. When I clicked on the 28 number a list of the racks was
presented. The site column showed the new site/location in the list. The
search field on the right showed the old site name as the filter.

On Thu, Apr 29, 2021 at 6:01 AM Jeremy Stretch @.***>
wrote:

I'm not able to reproduce the reported behavior following the steps
provided. Please elaborate on your steps above to start with the creation
of each object, and detailing exactly what actions you are taking at
each step.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netbox-community/netbox/issues/6305#issuecomment-829177717,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQD62BVFT53VNM5S6IYSD3TLFDDHANCNFSM43X74VLQ
.

@karrots commented on GitHub (Apr 29, 2021): Objects existed before the migration to 2.11 Objects moved were rack groups now locations. I moved the location to a different site as part of a consolidation of sites. The individual racks assigned to that location showed the new site in their pages. When opening a rack it showed the updated site. When looking at the old site stats page it still listed 28 racks when it should have listed 0. When I clicked on the 28 number a list of the racks was presented. The site column showed the new site/location in the list. The search field on the right showed the old site name as the filter. On Thu, Apr 29, 2021 at 6:01 AM Jeremy Stretch ***@***.***> wrote: > I'm not able to reproduce the reported behavior following the steps > provided. Please elaborate on your steps above to start with the creation > of each object, and detailing *exactly* what actions you are taking at > each step. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netbox-community/netbox/issues/6305#issuecomment-829177717>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABQD62BVFT53VNM5S6IYSD3TLFDDHANCNFSM43X74VLQ> > . >
adam commented 2025-12-29 19:21:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 4, 2021):

You need to run the provided upgrade script (upgrade.sh) per the documented upgrade process. This includes a command which clears the entire cache (manage.py invalidate all).

@jeremystretch commented on GitHub (May 4, 2021): You need to run the provided upgrade script (`upgrade.sh`) per the [documented upgrade process](https://netbox.readthedocs.io/en/stable/installation/upgrading/). This includes a command which clears the entire cache (`manage.py invalidate all`).
adam commented 2025-12-29 19:21:13 +01:00
Author
Owner
Copy Link

@karrots commented on GitHub (May 4, 2021):

ok I'll ensure that ran and test. I'm using the netbox-docker container and
I'm pretty sure it runs that script. Can't confirm if it had issues this
time. The moves happened after the upgrade.

@karrots commented on GitHub (May 4, 2021): ok I'll ensure that ran and test. I'm using the netbox-docker container and I'm pretty sure it runs that script. Can't confirm if it had issues this time. The moves happened after the upgrade.
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 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#4845
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?