We store this information (whether or not the script maas-import-isos needs to be run) in a value that is cached using Django's cache. However, we're using a cache local to each thread (see CACHES in src/maas/settings.py) so the script maas-import-isos does not clear the WSGI application's cache (it calls "maas clearcache --key=profile-check-done").
A proper fix would be to use a shared cache using memcache.
An easy workaround is to reduce PROFILE_CHECK_DELAY in src/maasserver/middleware.py to a few seconds.
We store this information (whether or not the script maas-import-isos needs to be run) in a value that is cached using Django's cache. However, we're using a cache local to each thread (see CACHES in src/maas/ settings. py) so the script maas-import-isos does not clear the WSGI application's cache (it calls "maas clearcache --key=profile- check-done" ).
A proper fix would be to use a shared cache using memcache.
An easy workaround is to reduce PROFILE_CHECK_DELAY in src/maasserver/ middleware. py to a few seconds.