Bug 2069807 - Internal Image registry with GCS backend does not redirect client
Summary: Internal Image registry with GCS backend does not redirect client
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: Yaxin You
Depends On: 2065689
TreeView+ depends on / blocked
Reported: 2022-03-29 18:13 UTC by Oleg Bulatov
Modified: 2022-04-08 05:04 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2065689
Last Closed: 2022-04-08 05:04:53 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift image-registry pull 321 0 None open Bug 2069807: Bug 2060362: Revert "Support authentication using gcp workload identity federation" 2022-03-30 21:19:22 UTC
Red Hat Product Errata RHSA-2022:1162 0 None None None 2022-04-08 05:04:57 UTC

Comment 7 XiuJuan Wang 2022-04-01 01:19:55 UTC
Report new bug https://bugzilla.redhat.com/show_bug.cgi?id=2070791 to track image registry broken issue on gcp workload identity enabled cluster.

Comment 9 XiuJuan Wang 2022-04-02 02:20:12 UTC
Since 4.10.0-0.nightly-2022-03-31-213412 is rejected, but 4.10.7-x86_64 has bump out with the fix merged.
Verified on 4.10.7-x86_64

Comment 11 W. Trevor King 2022-04-07 05:45:53 UTC
Clearing UpgradeBlocker from this bug.  If folks want to talk about update-recommendation changes, we should keep that discussion collected in the series tip bug 2065689.  Although I've just dropped UpgradeBlocker there too [1].

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=2065689#c10

Comment 12 errata-xmlrpc 2022-04-08 05:04:53 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.10.8 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.


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