+++ This bug was initially created as a clone of Bug #1758424 +++ As Glance is now able to configure the multiple stores, in distributed compute case it is possible that same image is present/copied across multiple stores. As of now the image can be copied to different locations manually by admin/operator and then same will be updated to image locations using locations API. If admin/operator want to delete the image from one of the available stores then he need to use the current vulnerable locations API to do so as delete API will simply deletes the image from all of its available locations. In order to get rid of vulnerable locations API to delete the image from one of the store, Glance should enhance the delete API which will be able to delete the image from provide store(s). --- Additional comment from Erno Kuvaja on 2019-12-10 12:57:41 CET --- Patch in flight https://review.opendev.org/#/c/698049/ and the spec https://review.opendev.org/#/c/698018/ --- Additional comment from Abhishek Kekane on 2020-03-16 07:35:36 CET --- Specs and API side patch merged. Patch https://review.opendev.org/#/c/698049/ and the spec https://review.opendev.org/#/c/698018/ client side patch under review: https://review.opendev.org/#/c/699644/ --- Additional comment from Cyril Roelandt on 2020-04-22 22:56:13 CEST --- This also requires python-glanceclient-2.17.0-0.20200310160931.40c19aa.el8ost. --- Additional comment from Gregory Charot on 2020-04-23 11:19:23 CEST --- Since the team has been able to complete upstream work in time as well as downstream backport, I'm moving this RFE to 16.1.1 --- Additional comment from RHEL Program Management on 2020-04-25 00:47:15 CEST --- This item has been properly Triaged and planned for the release, and Target Release is now set to match the release flag. For details, see https://mojo.redhat.com/docs/DOC-1195410 --- Additional comment from errata-xmlrpc on 2020-05-06 22:31:58 CEST --- This bug has been added to advisory RHBA-2020:54415 by Lon Hohberger (lhh) --- Additional comment from errata-xmlrpc on 2020-05-06 22:31:59 CEST --- Bug report changed to ON_QA status by Errata System. A QE request has been submitted for advisory RHBA-2020:54415-01 https://errata.devel.redhat.com/advisory/54415
I don't really understand why a clone of Bug #1758424 is required. The patch for this feature has been merged downstream (see https://code.engineering.redhat.com/gerrit/#/c/197394/) and is available in openstack-glance-19.0.3-0.20200313113446.3e16bc7. What is the difference between #1758424 and #1845422 ?
My understanding is that this feature has already been verified by Mike for bz#1758424. Should we mark this bug as VERIFIED already?
@Mike: I agree, this could be marked as VERIFIED.
According to our records, this should be resolved by openstack-glance-19.0.3-0.20200421223424.3e16bc7.el8ost. This build is available now.