···
#
#
# One of the configured repositories failed (Zoo),
# 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 Default_Organization_Test_Product_Zoo
#
# 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=Default_Organization_Test_Product_Zoo.skip_if_unavailable=true
#
# failure: repodata/repomd.xml from
Default_Organization_Test_Product_Zoo: [Errno 256] No more mirrors to
try.
# https://katello-centos7-bats.example.com/pulp/repos/Default_Organization/Test/Test_CV/custom/Test_Product/Zoo/repodata/repomd.xml:
[Errno 14] HTTPS Error 404 - Not Found
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
> If anyone has time, or insight into the current pipeline failure, it
> would be greatly appreciated. The failure is:
To provide an update on this, the dependency issues were resolved and we
were able to then reproduce the issue described by this email. The
following PRs were opened and merged to fix it:
>> If anyone has time, or insight into the current pipeline failure, it
>> would be greatly appreciated. The failure is:
> To provide an update on this, the dependency issues were resolved and
> we were able to then reproduce the issue described by this email. The
> following PRs were opened and merged to fix it:
>
> https://github.com/Katello/puppet-pulp/pull/101
> https://github.com/Katello/puppet-katello/pull/86
>
> After those were merged the bats tests failed with a new error that
> should be resolved by https://github.com/Katello/katello/pull/5504
>
> Thanks john for that fix!
>
> We should know shortly if there are any other issues.
>
> -Justin
This is now resolved and the pipeline is green.
-Justin
···
On 09/29/2015 05:45 PM, Justin Sherrill wrote:
> On 09/22/2015 02:27 PM, Eric D Helms wrote:
not ok 31 install package from content view
(from function `tIsRedHatCompatible’ in file os_helper.bash, line 4,
from function `tPackageInstall’ in file os_helper.bash, line 89,
