Tagged RPM pipeline failing when trying to publish to repo
Summary
Last Friday we tagged a new release but the pipeline for the publishing of the RPMs to CTA Repo had some errors, thus, the repo was not correctly built.
What is the current bug behaviour?
Error for tag el9#v5.10.10.0-1.el9
, pipeline job:
Critical: Cannot rename ./.repodata/ -> ./repodata/: cp: cannot stat './.repodata/': No such file or directory : Child process exited with code 1
Directory walk started
Directory walk done - 3025 packages
Temporary output repo path: ./.repodata/
Preparing sqlite DBs
Pool started (with 5 workers)
Pool finished
HOOK executed successfully
Cleaning up project directory and file based variables 00:00
Job succeeded
Error for tag v5.10.10.0-1
, pipeline job:
C_CREATEREPOLIB: Warning: cr_repomd_record_fill: File ./.repodata//primary.sqlite.bz2 doesn't exists
C_CREATEREPOLIB: Warning: cr_repomd_record_fill: File ./.repodata//filelists.sqlite.bz2 doesn't exists
C_CREATEREPOLIB: Warning: cr_repomd_record_fill: File ./.repodata//other.sqlite.bz2 doesn't exists
C_CREATEREPOLIB: Critical: rename_file: Cannot rename ./.repodata//primary.xml.gz to ./.repodata//f2e37914efc294fb437df3e37da74aa73444e6308e3294cfea682c4495fe9d8f-primary.xml.gz
C_CREATEREPOLIB: Critical: rename_file: Cannot rename ./.repodata//filelists.xml.gz to ./.repodata//0ad76b8816fc23d18923562edd24e58e3f818894a2ceaa7eaadf186323d37a19-filelists.xml.gz
C_CREATEREPOLIB: Critical: rename_file: Cannot rename ./.repodata//other.xml.gz to ./.repodata//bf0f0759b522726a23840015eaf85f25e90968d4a696a7d6f8b60428b134e038-other.xml.gz
Error for tag v4.10.10.0-1
, pipeline job
Warning: Permanently added 'lxplus.cern.ch,188.185.10.8' (ECDSA) to the list of known hosts.
Critical: Cannot open file ./.repodata//primary.xml.gz: File already exists
Directory walk started
Directory walk done - 3025 packages
Temporary output repo path: ./.repodata/
HOOK executed successfully
Objectives
- Debug and fix procedure to publish the CTA RPMs.
- Add CI stage to validate that the RPMs have been successfully published and that the repo is working properly.