I need advices about how to fix this since the switch to zck compression, our koji builder cannot parse the fedora rawhide metadata. This would requires createrepo_c 1.0.x that support zck, but using this version has new problems: - Is produce zck compressed metadata that cannot be read by older yum (that can be tuned by patching kojid builder to specity the compressed output). - It consumes lot more memory (many OOM on our 5G koji builders whereas 4G is usually enough for regen-repo task) - It produces a repomd.xml with only a compressed comps that cannot be read by EL7 yum. (see https://github.com/rpm-software-management/createrepo_c/issues/403 )
Using our version of createrepo_c in our fedora builders shows: C_CREATEREPOLIB: Critical: cr_metadata_load_xml: Error encountered while parsing C_CREATEREPOLIB: Critical: Cannot load repo: "http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/aarch64/os/" C_CREATEREPOLIB: Critical: cr_metadata_load_xml: Error encountered while parsing Critical: Cannot load repo: "http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/aarch64/os/" : Error encountered while parsing:primary.xml parsing: Cannot open /tmp/createrepo_c_tmp_repo_NbYHix/repodata/7cd966d76cea90afb8aef04eafa414f098c37128f99c7da74cc57114643915d0-primary.xml.zst: Cannot detect compression type
This looks to be a duplicate of #11631
Yep, except that fedora koji doesn't consume the repodata produced by pungi. So if pungi "workarounds" the issue in #11631, the problem will rise again when builders will be updated to createrepo_c 1.0.x from fedora-39+
Best solution, that I suggested upstream. https://github.com/rpm-software-management/createrepo_c/issues/403#issuecomment-1822622405 Would imply a --compatibility mode...
So to me is a different issue as it deals with others components and could have other solutions. But the cause is similar (createrepo_c changed defaults).
OK thanks for pointing out the differences.
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
I'm switching rawhide back to gzip for now... of course yes, this will be an issue when/if we upgrade builders to f39 in prod for epel7 builds...
Metadata Update from @kevin: - Issue untagged with: medium-gain, medium-trouble, ops - Issue priority set to: Needs Review (was: Waiting on Assignee)
I've tried to move rawhide back to gz for now... if a compose ever finishes with that we can at least kick this issue down the road some.
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
So, rawhide is back on gz for now... I asked what we should do in #11631
We still need to sort this related problem before upgrading any prod builders to 39. Hopefully the --compatibility thing will become supported by koji/createrepo_c soon.
So, I might just upgrade our builders, but Epoch the old createrepo_c... since there doesn't seem to be much movement to fix this in koji/createrepo_c currently. ;(
The moving forward:
So, we don't want to break epel7... so nothing should change in repodata until rhel7 EOL.
So, I think we can close this and just work in other places for longer term/better fixes.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
FYI, upstream creatrepo_c has grown a --compatibility option https://github.com/rpm-software-management/createrepo_c/issues/403
I also suggested to change the default behavior of the createrepo command to retain --compatibility by default https://github.com/rpm-software-management/createrepo_c/pull/420 If that's merged, we woun't need any patch for koji (just disabling createrepo_c in kojid.conf) would be enought to generate metadata compatible with el7.
That until koji has a fine tuned option to provide arbitrary parameters to the createrepo_c command.
Comments are welcomed (on the PR, remaining point).
Yeah, in the mean time I moved our builders to f39, but pushed a pre 1.0 createrepo_c with a Epoch:1 for now.
Once koji can adjust this we can drop that and switch. Or if rhel7 goes eol before then, we can just drop it and drive on.
Hopefully we are ok until then. Thanks for all your efforts moving this forward... hopefully something will move.
Login to comment on this ticket.