Fixing test flake for docker builds #8846
Conversation
The problem appears to be triggered by a small number of epel mirrors. In the
past this sort of problem has been solved by upgrading nss. I updated nss
inside the centos7 container and still saw the problem. Only when I updated
openssl-libs did the problem seem to disappear.
Below you can see the error message:
---------------------------
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable <repoid>
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
|
[test] |
|
@dobbymoodge, fyi, I seen you've been doing some work recently on the base_ami job. Have you noticed this failure? |
|
@brenton I haven't looked into this particular issue before, but I see where it's happened a few times. LGTM. |
|
fixes #8571 |
|
Doing some more testing to make sure this isn't just wishful thinking. |
|
Hmm, I ran a few hundred more tests and still saw one failure. I don't think this solves the problem. |
|
Actually, the failure I just saw was similar but for a core centos repository and not epel. |
|
|
|
[test] |
1 similar comment
|
[test] |
|
Evaluated for origin test up to 606c905 |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/3838/) |
|
LGTM [merge] |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/5917/) (Image: devenv-rhel7_4208) |
|
Evaluated for origin merge up to 606c905 |
The problem appears to be triggered by a small number of epel mirrors. In the
past this sort of problem has been solved by upgrading nss. I updated nss
inside the centos7 container and still saw the problem. Only when I updated
openssl-libs did the problem seem to disappear.
Below you can see the error message:
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again