Bug 2015800 - [IBM]Shouldn't change status.storage.bucket and status.storage.resourceKeyCRN when update sepc.stroage,ibmcos with invalid value
Summary: [IBM]Shouldn't change status.storage.bucket and status.storage.resourceKeyCRN...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.10
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.11.0
Assignee: Oleg Bulatov
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks: 2048117
TreeView+ depends on / blocked
 
Reported: 2021-10-20 06:36 UTC by XiuJuan Wang
Modified: 2022-08-10 10:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 10:39:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
registry operator logs (138.50 KB, application/x-tar)
2022-01-27 05:55 UTC, XiuJuan Wang 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 742 0 None open Bug 2015800: fix(ibmcos): Resource key validation + update status granularly 2022-01-27 23:04:41 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:39:33 UTC

Comment 2 XiuJuan Wang 2022-01-27 05:55:07 UTC 
Created attachment 1855698 [details]
registry operator logs
Comment 3 XiuJuan Wang 2022-01-28 04:06:38 UTC 
Can't reproduce the bug issues with pr build version.
When update storage with invalid value, the change can't be sync to status.storage.
Comment 7 errata-xmlrpc 2022-08-10 10:39:06 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.