There are also at least one file with incorrect size & checksum in file d84790843c77fc2bae170d90b42594a73ebf72109ff56a7d860bf2ad6ee351a0-primary.xml.gz:
Confirmed. I’m seeing issues syncing BaseOS, PowerTools, and AppStream using Katello.
The Plus repo syncs successfully, and imported Errata details for an openldap bugfix. Perhaps the issue with syncing these other repos is related to the new errata system?
This is a pretty major concern for many of us who are using / plan to use Rocky in the Enterprise, with central patch management functions and features.
Any word on when this may be resolved?
Thanks for your help and excellent work on this project!
i was in the same situation Solved it like that:
synced it to a mirror (i’ve used AT Mirrors - Mirror Manager )
next i’ve changed the upstream URL to Index of /pub/rocky/8/BaseOS/x86_64/os/
and synced it via Advanced Sync - Complete Sync
Synced correctly
I did similar as a work around but that should not be the solution.
There are no issues to sync Alma Linux directly with katello (Foreman) and Rocky should work the same way.
Change the upstream URL to AT: https://mirror.alwyzon.net/rockylinux/8/AppStream/x86_64/os/
Run a sync (Select Action → Sync Now)
Change the upstream URL back to the Rocky baseurl: https://dl.rockylinux.org/pub/rocky/8/AppStream/x86_64/os/
Run a Complete Sync (Select Action → Advanced Sync → Complete Sync)
…and eliminate the error??
In my experience, this doesn’t work. I’ve even attempted completely deleting one of the three problematic repos, deleting orphaned content, and recreating it, and I still get the error, even when the new repo is created to source from dl.rockylinux.org from the get-go.
Not sure how jlhm got it working, but in my case I sync Katello against an internal mirror. I deleted the line <open-size></open-size> from the repomd.xml file and now the sync is working. I’ve tested it with BaseOS, AppStream, and HighAvailability.
I checked against a random CentOS repomd.xml file and it doesn’t have a <open-size></open-size> within this one specific block of code.
So to me the issue is with the Rocky repomd.xml files online that will need to be regenerated
My solution was to use reposync on a host that downlooad all rpm files. Then I used createrepo to create the repodata files and then modifyrepo command to add modules and update info to the repo. After that I use Foreman (katello) to get the repo from that repo I just created.
Example:
@brian.earl and @jlhm – Yeah, that’s really running around Robin Hood’s barn. Okay, I’ve just reached out to https://chat.rockylinux.org with this insight to see if we can get some visibility on this. I didn’t see it already in discussion, based on search terms I used.
Edit: @jlhm , @almor , and @brian.earl – There has (already!) been follow-up to the BZ submitted earlier this afternoon. The outstanding issue with the repomd.xml appears to have been resolved.