STS work in 4.7 lacks Image Registry support, the linked PRs are outstanding and have previously been verified by CCO QE teams.
CCO and Image Registry QE teams should coordinate to make sure that both teams are familiar with the work.
Installed a cluster at version 4.7.0-0.nightly-2021-02-12-013204 following the instructions in comment 17 and registry pushes are working well. I will trigger QE automation against this cluster, but I think we can mark this issue VERIFIED or CLOSED UPSTREAM.
(In reply to Mike Fiedler from comment #20)
> Installed a cluster at version 4.7.0-0.nightly-2021-02-12-013204 following
> the instructions in comment 17 and registry pushes are working well. I
> will trigger QE automation against this cluster, but I think we can mark
> this issue VERIFIED or CLOSED UPSTREAM.
Thanks for your follow up, Mike!
I also cannot reproduce this bug by triggering 10 builds on 4.7.0-rc.2 now:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-rc.2 True False 3h1m Cluster version is 4.7.0-rc.2
$ oc get builds
NAME TYPE FROM STATUS STARTED DURATION
rails-postgresql-example-5 Source Git@9e6fe17 Complete 16 minutes ago 2m32s
rails-postgresql-example-6 Source Git@9e6fe17 Complete 14 minutes ago 2m30s
rails-postgresql-example-7 Source Git@9e6fe17 Complete 11 minutes ago 2m16s
rails-postgresql-example-8 Source Git@9e6fe17 Complete 9 minutes ago 2m16s
rails-postgresql-example-9 Source Git@9e6fe17 Complete 7 minutes ago 2m15s
rails-postgresql-example-10 Source Git@9e6fe17 Complete 4 minutes ago 2m17s
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.7.1 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.