New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1919453: [release-4.6] configure tests to pull images from mirror #26729
Bug 1919453: [release-4.6] configure tests to pull images from mirror #26729
Conversation
@rvanderp3: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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. |
Skipping CI for Draft Pull Request. |
6be318d
to
66e920a
Compare
@rvanderp3: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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. |
@rvanderp3: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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. |
@rvanderp3: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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. |
/bugzilla refresh |
@rvanderp3: An error was encountered querying GitHub for users with public email (bandrade@redhat.com) for bug 1919453 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: i/o timeout
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this:
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. |
@rvanderp3: This pull request references Bugzilla bug 1919453, which is valid. 6 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (bandrade@redhat.com), skipping review request. In response to this:
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. |
/cc @bparees |
66e920a
to
ce61ff0
Compare
/approve |
/hold A possible regression in e2e-aws/e2e-gcp needs to be addressed. Will remove hold once done. |
bcb26ad
to
11eaaa1
Compare
11eaaa1
to
379aa4e
Compare
@rvanderp3: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/lgtm |
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, jcpowermac, rvanderp3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@rvanderp3: All pull requests linked via external trackers have merged: Bugzilla bug 1919453 has been moved to the MODIFIED state. In response to this:
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. |
The intention of this PR is to enable some tests in the
openshift/conformance/parallel
suite which are not subject to the mirror configuration in/etc/containers/registries.conf
to use a mirror as the source of their required images.Note: The pattern in this PR could be applied to other suites as well.
This is needed due to docker.io rate limiting causing CI on some platforms on 4.6 to be in permafail. To use the feature in this PR:
openshift-tests
,export TEST_IMAGE_MIRROR_REGISTRY=<pull-through-cache-host>:<port>
To enable resources which can take advantage of the mirror registry, apply a machine-config which configures the pull-through cache as a docker.io registry mirror. This will allow, over the course of a day or so(based on pull-rate exhaustion), for all required images to be pulled and cached.
This PR is an alternate to solution to that proposed in #26256