Bug 1869613 - [OSP] Errors are ignored during swift container deletion
Summary: [OSP] Errors are ignored during swift container deletion
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.6.0
Assignee: Mike Fedosin
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-18 11:09 UTC by Mike Fedosin
Modified: 2020-10-27 16:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:29:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 590 0 None closed Bug 1869613: don't ignore swift errors during container deletion 2020-10-01 08:10:18 UTC
Github openshift cluster-image-registry-operator pull 595 0 None closed Bug 1869613: Swift: add a unit test for bulk deleting failure 2020-10-01 08:10:17 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:29:38 UTC

Description Mike Fedosin 2020-08-18 11:09:08 UTC
Description of problem:

Currently when we destroy Swift image registry container with BulkDelete, all internal errors are ignored, which can lead to some obscure issues in the future.

Comment 3 Mike Fedosin 2020-08-26 08:35:59 UTC
We need to add a unit test for this case: https://github.com/openshift/cluster-image-registry-operator/pull/595

Comment 5 Wenjing Zheng 2020-09-09 09:54:30 UTC
The unit test which covers the scenario has been passed.

Comment 7 errata-xmlrpc 2020-10-27 16:29:05 UTC
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 (OpenShift Container Platform 4.6 GA Images), 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:4196


Note You need to log in before you can comment on or make changes to this bug.