Data remains in staging area if 'file' store is not enabled
When operator has not enabled 'file' store and using other stores like ceph,
swift etc. the uploading to staging area works as we explicitly
build 'file' store during this operation, while cleaning up we directly
use 'glance_store.delete_from_backend' which only works if 'file'
store is enabled.
Modified '_DeleteFromFS' task and _unstage call which will use os
module to unlink the file present in staging area explicitly to
delete the data from staging area.
Reviewed: https:/ /review. openstack. org/648610 /git.openstack. org/cgit/ openstack/ glance/ commit/ ?id=14e9e1ef868 759df2be67f7b61 ce3c41ec547ac2
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 14e9e1ef868759d f2be67f7b61ce3c 41ec547ac2
Author: Abhishek Kekane <email address hidden>
Date: Wed Mar 13 18:12:42 2019 +0000
Data remains in staging area if 'file' store is not enabled
When operator has not enabled 'file' store and using other stores like ceph, store.delete_ from_backend' which only works if 'file'
swift etc. the uploading to staging area works as we explicitly
build 'file' store during this operation, while cleaning up we directly
use 'glance_
store is enabled.
Modified '_DeleteFromFS' task and _unstage call which will use os
module to unlink the file present in staging area explicitly to
delete the data from staging area.
Conflicts:
glance/ async/flows/ api_image_ import. py
glance/ tests/unit/ async_/ flows/test_ web_download. py
NOTE: async_ module was not available in queens so renamed
the module name to async.
Closes-Bug: #1803498 1291758c6726789 0e0959ebb3c b56152d199cc0fe a049e4d4a7)
Change-Id: If0b3b0af930030
(cherry picked from commit c92724608512d42