This seems to be happening due to syncing issues, as 7.9.2009 was released and the link may be trying to point to http://vault.centos.org/centos/7.0.2009/updates/Source/repodata/repomd.xml, which still doesn't exist.
For now, AFAIU, it should still be pointing to the 7.8.2003 one.
This is impacting CRI-O / OpenShift CI as it used a CentOS 7 container underneath and it's failing as shown below:
* updates: mirror.ash.fastserv.com http://vault.centos.org/centos/7/updates/Source/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. failure: repodata/repomd.xml from updates-source: [Errno 256] No more mirrors to try. http://vault.centos.org/centos/7/updates/Source/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found [ERROR] hack/build-rpms.sh:34: `yum-builddep -y "${OS_RPM_SPECFILE}"` exited with status 1. subprocess exited with status 1 subprocess exited with status 1 error: build error: error building at STEP "RUN /bin/bash -c set -o errexit; umask 0002; hack/build-rpms.sh; ln -s $( pwd )/_output/local/releases/rpms/ /srv/repo": exit status 1 2020/11/13 10:37:32 No custom metadata found and prow metadata already exists. Not updating the metadata. 2020/11/13 10:37:33 Ran for 2m31s error: some steps failed: * could not run steps: step rpms failed: the build rpms failed after 1m4s with reason DockerBuildFailed: Dockerfile build strategy has failed. http://vault.centos.org/centos/7/updates/Source/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found [ERROR] hack/build-rpms.sh:34: `yum-builddep -y "${OS_RPM_SPECFILE}"` exited with status 1.
Link: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/cri-o_cri-o/4356/pull-ci-cri-o-cri-o-release-1.18-e2e-aws/1327198251580919808/build-log.txt
Metadata Update from @arrfab: - Issue assigned to hughesjr - Issue tagged with: centos-common-infra, low-gain, low-trouble
Hi,
Some just reported the same issue on centos-devel list, and it seems that @hughesjr indeed forgot to update metadata. (and also some real src.rpm should also have landed there, probably still in his todo list for post-GA activities)
I've created empty repodata for now, so that shouldn't "block" you but I'll let this ticket assigned so that he can confirm and close it when properly implemented
@arrfab,
Thanks a lot for the very quick response and even quicker workaround. It does "unblock" us, indeed, as I've just tested it.
Thanks a lot, @arrfab @hughesjr , btw, I remember this same issue happened at least once in the past (I think during the previous release), so just wanted to check if it's possible to do the symlink change 7 -> $LATEST_RELEASE going forward only after $LATEST_RELEASE repos are known to be working.
OK .. I have pushed the empty repodata files .. and i will push the srpms in a few minutes.
I have to put the new symlink in place so we can rsync all the sig content, etc, into vault for the new release.
OK .. srpms are on the way now .. these should be fixed in 30 or so minutes on vault.centos.org.
The sclo repos are still throwing a 404:
yum-builddep -y /home/user/rpmbuild/SPECS/puppet-extensions.spec Loaded plugins: fastestmirror, ovl Enabling base-source repository Enabling centos-sclo-rh-source repository Enabling centos-sclo-sclo-source repository Enabling epel-source repository Enabling extras-source repository Enabling updates-source repository http://vault.centos.org/centos/7/sclo/Source/rh/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. failure: repodata/repomd.xml from centos-sclo-rh-source: [Errno 256] No more mirrors to try. http://vault.centos.org/centos/7/sclo/Source/rh/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
the automatic sign + push for SIG content always go /centos/7/ but it seems that @hughesjr is just switching that symlink under /centos/7 to new major.minor but that of course lacks content from previous release, and so that breaks all SIG content directory as they aren't links
Content is still there : https://vault.centos.org/centos/7.8.2003/sclo/Source/rh
@hughesjr : how can we avoid this ? I'd be in favor or just os/updates/extras (that you manage manually) to be symlinks to real version, while for SIG (as it's fully automated and nobody is required) it would just continue to push to /centos/7/ (being a directory and not a link that you'd switch) ..
no news from @hughesjr here for days but normally fixed .. so closing ticket
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.