Recently I see some frequent koschei failure with failing to read package header, e.g.
https://koji.fedoraproject.org/koji/taskinfo?taskID=112475224 https://koji.fedoraproject.org/koji/taskinfo?taskID=112839582 https://koji.fedoraproject.org/koji/taskinfo?taskID=112636082
These show something like:
DEBUG util.py:463: [105/105] fedora-release-identity-basic 100% | 900.0 KiB/s | 10.8 KiB | 00m00s DEBUG util.py:463: -------------------------------------------------------------------------------- DEBUG util.py:463: [105/105] Total 100% | 3.3 MiB/s | 40.0 MiB | 00m12s DEBUG util.py:463: Running transaction DEBUG util.py:461: Failed to read package header from file "/var/cache/libdnf5/build-a089928214108df4/packages/libssh-config-0.10.6-4.fc40.noarch.rpm" DEBUG util.py:610: Child return code was: 1 DEBUG util.py:185: kill orphans in chroot /var/lib/mock/f40-build-48703068-5790430-bootstrap/root
(Packages failing to read header seems random) I don't know if this is due to dnf5, or koji network issue, or something else. Would you investigate this? Thank you.
More weird errors: even logs are unavailable:
https://koji.fedoraproject.org/koji/taskinfo?taskID=112847171 https://koji.fedoraproject.org/koji/taskinfo?taskID=112847118 https://koji.fedoraproject.org/koji/taskinfo?taskID=112843663
This seems to be a rpm and/or dnf5 bug.
I filed:
https://bugzilla.redhat.com/show_bug.cgi?id=2262344
on it.
Can you add your information there?
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Oh, the non log ones I think were because buildvm-s390x-18.s390.fedoraproject.org ran out of space. (Due to dnf5 caching). https://pagure.io/releng/issue/11929 (at least from a quick glance all those were on 18)
Log in to comment on this ticket.