After Upgrade to Django 5.2.9, Some Warnings from easy_thumbnail's thumbnail_cleanup

[jonfroehlich]

When we start the server, we run a script that also executes a series of cleanup commands (to remove stale or unused files from the filesystem). One of these commands is python manage.py thumbnail_cleanup, which executes easy_thumbnail's built-in thumbnail_cleanup command to remove old unused thumbnails. However, Django 5.2.9 changed how it handles default storage, so we get this warning.

The warnings are harmless—the cleanup command is just skipping orphaned records it can't locate. The site should still work fine. The thumbnails themselves will regenerate as needed.

website-1  | ****************** STEP 4.1/5: docker-entrypoint.sh ************************
website-1  | 4.1 Running 'python manage.py thumbnail_cleanup' to delete unused thumbnails
website-1  | ******************************************
website-1  | CONFIG_FILE: /code/config.ini
website-1  | DJANGO_ENV: None
website-1  | DEBUG_SET: DEBUG was set by /code/config.ini file
website-1  | DEBUG: True
website-1  | System check identified some issues:
website-1  |
website-1  | WARNINGS:
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
website-1  | Can't determine source storage, skipping source
website-1  | Source storage hash (f9bde26a1556cd667f742bd34ec7c55e) not found in STORAGES
...