If you set node_staging_uri=file:///var/lib/glance/staging and try to do a web-download import without the file store enabled, this is logged:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py", line 53, in _execute_task
result = task.execute(**arguments)
File "/usr/lib/python2.7/site-packages/glance/async_/flows/api_image_import.py", line 92, in execute
store_api.delete_from_backend(file_path)
File "/usr/lib/python2.7/site-packages/glance_store/backend.py", line 409, in delete_from_backend
loc = location.get_location_from_uri(uri, conf=CONF)
File "/usr/lib/python2.7/site-packages/glance_store/location.py", line 75, in get_location_from_uri
raise exceptions.UnknownScheme(scheme=pieces.scheme)
UnknownScheme: Unknown scheme 'file' found in URI
The consequence is that the staging area is not cleaned up, and files are piling up. The store should probably be automatically configured.
This is the case when operator has not enabled file store, i.e. he is using other stores like ceph, swift etc. In this situation, the uploading to staging area works as we explicitly build file store during this operation, while cleaning up we directly use glance_
This is not user-friendly, what I recommend for upstream fix is;
1. Document that in case if you want to use image-import api then 'file' store needs to be in the list of 'stores' defined in glance-api.conf
2. We can load file store at [1] and use store.delete method directly there.
[1] https:/
NOTE:
Once multiple backend is stabilized we will not face this issue as we will be reserving a file store for this purpose. (refer, https:/