Bug 2083559 - [IPI IBM]Can't create image-registry-private-configuration secret with error "specified resource key credentials does not contain HMAC keys"
Summary: [IPI IBM]Can't create image-registry-private-configuration secret with error ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Oleg Bulatov
QA Contact: XiuJuan Wang
Depends On: 2082492
Blocks: 2077419
TreeView+ depends on / blocked
Reported: 2022-05-10 10:52 UTC by OpenShift BugZilla Robot
Modified: 2022-05-23 13:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Changes to IBM Cloud Object Storage bucket permissions require now require Administrator role. Consequence: The OpenShift Image Registry Operator will not require Administrator role. Fix: The OpenShift Image Registry Operator requests Administrator role. Result: Clusters which utilize manual credential minting will require updates to the permissions granted to the credentials used by the Image Registry Operator.
Clone Of:
Last Closed: 2022-05-23 13:25:12 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 778 0 None Merged [release-4.10] Bug 2083559: IBMCloud: Add admin permissions to CR 2022-05-16 17:45:35 UTC
Red Hat Product Errata RHBA-2022:2258 0 None None None 2022-05-23 13:25:34 UTC

Comment 1 XiuJuan Wang 2022-05-11 07:23:00 UTC
Could install IPI on IBM cluster with pr https://github.com/openshift/cluster-image-registry-operator/pull/778 fixed

Comment 8 errata-xmlrpc 2022-05-23 13:25:12 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.10.15 bug fix 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.


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