Bug 1945690 - [4.6z] Dockerfile needs updating to new container CI registry
Summary: [4.6z] Dockerfile needs updating to new container CI registry
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Tim Rozet
QA Contact: zhaozhanqi
Depends On: 1945689
TreeView+ depends on / blocked
Reported: 2021-04-01 16:12 UTC by Tim Rozet
Modified: 2021-04-27 14:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1945689
Last Closed: 2021-04-27 14:20:49 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 401 0 None open Bug 1945690: Updating ose-ovn-kubernetes builder & base images to be consistent with ART 2021-04-01 16:18:41 UTC
Red Hat Product Errata RHBA-2021:1232 0 None None None 2021-04-27 14:21:10 UTC

Description Tim Rozet 2021-04-01 16:12:28 UTC
+++ This bug was initially created as a clone of Bug #1945689 +++

+++ This bug was initially created as a clone of Bug #1945687 +++

Description of problem:
In our downstream dockerfile we need to update 4.6 from
FROM registry.svc.ci.openshift.org/ocp/builder:...

FROM registry.ci.openshift.org/ocp/builder:...

in several places

This has already been done in 4.7 and 4.8, but need to do it for 4.6.

Comment 2 zhaozhanqi 2021-04-19 03:03:23 UTC
Verified this bug on 4.6.0-0.nightly-2021-04-17-182039
by checking: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-ovn-4.6/1383487188783599616

Comment 5 errata-xmlrpc 2021-04-27 14:20:49 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.6.26 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.