Skip to content

Registry-Replacer autoupdate#12532

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
openshift-bot:registry-replacer
Oct 8, 2020
Merged

Registry-Replacer autoupdate#12532
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
openshift-bot:registry-replacer

Conversation

@openshift-bot
Copy link
Copy Markdown
Contributor

This PR:

  • Adds a replacement of all FROM registry.svc.ci.openshift.org/anything directives found in any Dockerfile
    to make sure all images are pulled from the build cluster registry
  • Prunes existing replacements that do not match any FROM dircetive in the Dockerfile
  • Ensures the Dockerfiles used for promotion jobs matches the ones configured in ocp-build-data

@openshift-bot openshift-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Oct 8, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit f180f1a into openshift:master Oct 8, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-bot: Updated the ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:

  • key openshift-cluster-version-operator-master.yaml using file ci-operator/config/openshift/cluster-version-operator/openshift-cluster-version-operator-master.yaml
Details

In response to this:

This PR:

  • Adds a replacement of all FROM registry.svc.ci.openshift.org/anything directives found in any Dockerfile
    to make sure all images are pulled from the build cluster registry
  • Prunes existing replacements that do not match any FROM dircetive in the Dockerfile
  • Ensures the Dockerfiles used for promotion jobs matches the ones configured in ocp-build-data

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

wking added a commit to wking/cincinnati-operator that referenced this pull request Nov 16, 2020
The outgoing docker.io image was subject to docker.io rate limiting
[1]:

  error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: while pulling "docker://docker.io/openshift/origin-release:golang-1.13" as "docker.io/openshift/origin-release:golang-1.13"...

The new image matches openshift/cluster-version-operator@7cb2662924
(Updating cluster-version-operator builder & base images to be
consistent with ART, 2020-10-07,
openshift/cluster-version-operator#468).  Matching builders with the
CVO reduces our exposure by consolidating around a smaller set of Go
builder images.

I expect that after this lands, openshift/registry will pick it up via
a change like openshift/release@d0fa1c98b9 (Registry-replacer
autocommit, 2020-10-07, openshift/release#12532).

[1]: openshift#82 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants