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
Explicitly ref. quay images for CI #4828
Explicitly ref. quay images for CI #4828
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM at first glance, but might as well fix the instances in |
Yes. I was in a bit of a panic to open this but found in I'll add a commit to fix up references in bats. Thanks for the suggestion. |
How does this overlap with mirroring in |
That file is put in place from Edit: proxy is to |
Hmmm...thinking about this more, we maintain |
That file exists in the repository, so we shouldn't need to be overwriting it for CI. If CI is changing it, we need to update the copy in the repository, so that integration tests that aim to be usable outside of CI don't behave differently in hard-to-find ways when they're run outside of CI. There's also a case for setting CONTAINERS_REGISTRIES_CONF to point to the same file for unit and conformance tests, which I don't think we currently do, but it's worth remembering that when the conformance tests build an image using dockerd, it's still almost certainly going to be ignored. |
Yes, I agree. CI doesn't change the file. I looked through the scripts and Makefile and it looks like for the most part we reference the
Right, excellent point - conformance tests use docker, not podman. So we do need the the conformance tests pointing explicitly at I'm guessing there's no docker-equivalent for |
Not that I'm aware of. The |
9a9036c
to
c72f4ef
Compare
@edsantiago PTAL (careful) at the second commit that touches all non-conformance test files. My hope is that it's optional in terms of needing to backport to all release branches. Though if you prefer I can squash everything down into a single commit. |
c72f4ef
to
6155bae
Compare
Woops, force-push: Fixed missed conformance test update. |
tests/helpers.bash
Outdated
echo -n docker.io/library/"${img##*/}" | ||
echo -n quay.io/libpod/"$img" | ||
elif [[ quay.io/libpod/"${img##*/}" == "$img" ]] ; then | ||
echo -n quay.io/libpod"${img##*/}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@edsantiago I think maybe these test-failures are caused by my changes here. Should I have done:
echo -n quay.io/libpod"${img##*/}" | |
echo -n quay.io/libpod/"${img##*/}" |
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I'm reading it right, can't this clause be dropped?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ed seems busy, let me just try removing it...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ed seems busy, let me just try removing it...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I just have nothing to add. This is not my code, I don't even understand what it does or is supposed to do. I stand by anything @nalind says about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh okay, thanks for the update Ed.
6155bae
to
190b8dc
Compare
force-push: Rebased and tried removing second clause in |
LGTM |
Sigh...I think maybe I need to break this PR up since the first commit (conformance test) fixes a problem occurring on CI for basically every release branch. |
Commit beae564 updated the conformance test references to a deprecated repository. However, by pointing at the docker-hub it inadvertantly introduce a significant possibility for flakes. This is because anonymous docker hub access is rate-limited by IP. We cannot predict the IP used for CI VMs & Containers, any of which could be at or close to the limit. Fix this by pointing explicitly at a `quay.io/libpod/centos` repo. which is excluesively for use by CI, with static images. Signed-off-by: Chris Evich <cevich@redhat.com>
190b8dc
to
5a83012
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with two nits: one, I'd be happier if the commit title explicitly included "conformance tests" to make it clear that this doesn't touch bats tests; and second, below. Neither of them is worth blocking for, I'm just commenting in the unlikely event that you need to repush.
@@ -1,3 +1,4 @@ | |||
# Note: a registries.conf alias should redirect this to quay.io/libpod/busybox |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The word "should" is inherently ambiguous and should not be used in documentation (see what I did there?) In this instance, it's not clear whether you mean "we hope this happens", or "we know this will happen because there is an existing registries.conf mapping", or "we should some day set up a registries.conf mapping". This is fine to fix in the followup PR.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cevich, edsantiago, flouthoc, rhatdan 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 |
What type of PR is this?
/kind other
What this PR does / why we need it:
Commit cevich@beae564 updated the conformance test references to a
deprecated repository. However, by pointing at the docker-hub it
inadvertantly introduce a significant possibility for flakes. This is
because anonymous docker hub access is rate-limited by IP. We cannot
predict the IP used for CI VMs & Containers, any of which could be at or
close to the limit. Fix this by pointing explicitly at a
quay.io/libpod/centos
repo. which is excluesively for use by CI, withstatic images.
How to verify it
Conformance testing in CI will pass
Which issue(s) this PR fixes:
Special notes for your reviewer:
Ref: #4819
Does this PR introduce a user-facing change?