Bug 1806757 - [4.4][swift]image-registry crashes if change managementState from Removed to Managed for old swift container is forbidden to be removed
Summary: [4.4][swift]image-registry crashes if change managementState from Removed to ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 4.4.0
Assignee: Oleg Bulatov
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On: 1785534
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-24 22:32 UTC by Adam Kaplan
Modified: 2020-05-04 11:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: the image registry operator didn't cleanup storage status when it were removing storage Consequence: when the registry was switched back to managed, it wasn't able to detect that storage needs to be bootstrapped. Fix: cleanup storage status Result: the operator creates storage when it's switched back to managed state
Clone Of: 1785534
Environment:
Last Closed: 2020-05-04 11:39:25 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 467 0 None closed [release-4.4] Bug 1806757: fix regression 2020-04-17 10:10:17 UTC
Github openshift cluster-image-registry-operator pull 478 0 None closed [release-4.4] Bug 1806757: remove storage status when storage is removed 2020-04-17 10:10:17 UTC

Comment 3 Wenjing Zheng 2020-02-27 09:43:48 UTC 
Still can saw the issue on latest 4.4.0-0.nightly-2020-02-27-020932
$ oc adm release info registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-02-27-020932 --commits | grep image-registry-operator
  cluster-image-registry-operator                https://github.com/openshift/cluster-image-registry-operator                1d89d08850a112c4d79a492430b6120752b2c62f
Comment 9 Wenjing Zheng 2020-03-03 06:08:16 UTC 
Verified on 4.4.0-0.nightly-2020-03-02-231151.
Comment 11 errata-xmlrpc 2020-05-04 11:39:25 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, 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:0581
Note You need to log in before you can comment on or make changes to this bug.