If copying existing image in other stores fails while staging the data to staging directory due to power, network or any other reason. Then subsequent try may lead to data leaks in stores.
Is there a way for the admin to cleanup after a failed copy, and prevent the data leak?
(In reply to Cyril Roelandt from comment #1) > Is there a way for the admin to cleanup after a failed copy, and prevent the > data leak? At the moment Admin needs to manually check if there is any data leak and clear it.
@Abhishek: We currently have some CI issues with another 16.1 patch, once this is fixed I'll add this patch. Thanks for the upstream work!
This issue has conditional approval for 16.1 Z1 release, it must be in the first compose and tested before release of 16.1.1. If not, we will move to TM=Z2.
According to our records, this should be resolved by openstack-glance-19.0.3-0.20200421223423.3e16bc7.el8ost. This build is available now.
The fixed-in-version appears to be incorrect. The patch referenced was not included in the noted build.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (openstack-glance bug fix advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3570