After adding centos8s-buildroot external repo to CloudSIG repos, we can't longer use the el8 repo from outside.
Reproduce:
[validated] name=validated enable=1 gpgcheck=0 baseurl=http://cbs.centos.org/kojifiles/repos/cloud8s-openstack-xena-el8-build/latest/x86_64/
# dnf install --disablerepo="*" --enablerepo=validated glibc
it fails with:
[MIRROR] glibc-langpack-en-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-langpack-en-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-common-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-common-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-langpack-en-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-langpack-en-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-common-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-common-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-langpack-en-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-langpack-en-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-common-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-common-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [MIRROR] glibc-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org] [FAILED] glibc-2.28-161.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for http://kojifiles.rdu2.centos.org/kojifiles/repos/dist-c8-stream-build/latest/x86_64/toplink/packages/glibc/2.28/161.el8/x86_64/glibc-2.28-161.el8.x86_64.rpm [Could not resolve host: kojifiles.rdu2.centos.org]
Note that we use that repo to test builds created in CBS.
So the first thing : normally people aren't supposed to point directly to cbs repositories for "testing" ... that's what -testing tag is supposed to be used for, and so pushed out ... Some SIGs are using ci.centos.org to grab from -candidate for initial testing and it's all good but don't know why you're pointing to cbs.centos.org for unsigned pkgs either ...
Do you want us to so disable these buildroot repositories for now ?
Our use-case is not testing but building RPMs with mock in the CI jobs, hence the need to access buildroot repos.
In any case, it's confusing if publicly accessible repodata points to non-public URLs.
as it's not possible (yet) you have two choices :
sed s/kojifiles..../koji.mbox..../g
centos8s-buildroot
Let me know your choice :)
When we modify a spec file, we first do a scratch build in CBS, then we take the created RPMs and try to install them using mock. To make sure we have the same content in mock that we have in the buildroot, we add the repository http://cbs.centos.org/kojifiles/repos/cloud8s-openstack-xena-el8-build/latest/x86_64/ (or equivalent) as it has the exact packages combination.
If installs work fine, then we can merge and build them safely and then promote.
Other use case, would be to build packages locally with mock with same content as in CBS, but tbh we usually don't do it, although I'd say it should be a supported use case.
Yes, I'd say it's the best option until we have a better solution.
ack .. removed from all the initially asked tags, closing for now. Once internal cbs will be able to reach centos8s-buildroot the same way as it's possible externally, we can revisit if you want.
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
ack, thanks. In the meanwhile I'll see if we can convert the jobs to use other repos.
Log in to comment on this ticket.