Description of problem: Kickstarting the RHEL 9 beta from Red Hat repositories gives errors when attempting to download certain packages. Example message from failed kickstart: WRN packaging: Failed to download ‘shim-x64-15-16.el8.x86_64.rpm’: 3 - Interrupted by header callback: Server reports Content-Length: 682476 but expected size is: 683844 This happens with other packages if the system is set to BIOS instead of EFI, I saw the same message for python3-systemd-234-18.el9.x86_64.rpm Additionally, if I change the sync policies of those repos from on-demand to immediate I see warnings on the sync about checksums from Red Hat's cdn not matching. Verifying the checksums doesn't appear to make this go away. I was discussing this in Foreman's community forums here: Version-Release number of selected component (if applicable): Pulp3 How reproducible: Steps to Reproduce: 1. Have an installation of Satellite 6.10 2. Sync RHEL 9 beta kickstart repositories 3. Attempt kickstart Actual results: WRN packaging: Failed to download ‘shim-x64-15-16.el8.x86_64.rpm’: 3 - Interrupted by header callback: Server reports Content-Length: 682476 but expected size is: 683844 Expected results: Successful kickstart Additional info:
@lzap or @thatguy, what is the specific URL that was used?
(In reply to Daniel Alley from comment #2) > @lzap or @thatguy, what is the specific URL that was used? Ultimately it's coming from https://cdn.redhat.com/content/beta/rhel9/9/x86_64/baseos/kickstart/Packages/shim-x64-16-16.el8.x86_64.rpm
For the record, we have handed the problem over to the internal CDN team as it turned out there is a problem with the package or metadata. They have informed us that it should be now corrected. What is the fix for downstream users then? Just re-syncing? Thanks for help with this one.
Apologies dralley for the misclick. I was asking the other Daniel. Cheers!
That is also me but I'm now wondering how my school email address from 5 years ago got into the option list :) Yes, just re-syncing should be enough.
(In reply to Daniel Alley from comment #10) > That is also me but I'm now wondering how my school email address from 5 > years ago got into the option list :) > > Yes, just re-syncing should be enough. Looks like it's moving in the right direction, but now I see similar errors on other packages: For example I now see the same error on shim-ia32-15-16.el8.x86_64. rpm on the BaseOS kickstart repo and python3-dns-2.1.0-6.el9.noarch.rpm from the AppStream kickstart repo. I suspect there may be others, these are just the first ones to throw an error
Apologies @thatguy The distribution team is going to do an audit / refresh to get those packages replaced, we'll let you know when that is finished (and run a full sync to verify ourselves).
Looks like the updates are starting to flow through the system, will notify you when things seem to be fully updated. The TL;DR on this issue is that the RHEL 9 beta kickstart repos were slightly out of sync with the standard RHEL 9 beta repos due to an oversight in some processes that only applied to the beta.
I was able to do a successful immediate-mode sync of the repo, it should now be resolved.
(In reply to Daniel Alley from comment #14) > I was able to do a successful immediate-mode sync of the repo, it should now > be resolved. I can confirm BaseOS is working as expected Still running into a checksum issue on AppStream, now the package it's complaining about is CUnit-2.1.3-25.el9.x86_64.rpm
The updates to that repo might still be rolling out but I'll double check with them.
It was a caching issue, the issue was "fixed" but the caches hadn't been flushed yet and it was still serving the old RPM. Now though, I am able to sync AppStream successfully. Thanks for your patience!
(In reply to Daniel Alley from comment #17) > It was a caching issue, the issue was "fixed" but the caches hadn't been > flushed yet and it was still serving the old RPM. > > Now though, I am able to sync AppStream successfully. Thanks for your > patience! Of course,it is beta after all. I can confirm that I was able to successfully sync as well. Thanks for all your help with this
Hey, I just wanted to follow up and say I'm seeing some of the same issue in the non-kickstart AppStream repo, there were a few different packages and I don't remember all of them but gitk was definitely one of them
I was able to sync https://cdn.redhat.com/content/beta/rhel9/9/x86_64/appstream/os/ successfully. Is this the repo URL you're referring to or a different one?
(In reply to Daniel Alley from comment #20) > I was able to sync > https://cdn.redhat.com/content/beta/rhel9/9/x86_64/appstream/os/ > successfully. Is this the repo URL you're referring to or a different one? Yes, that the URL I'm referring to
Can you still reproduce the issue if you try again?
(In reply to Daniel Alley from comment #22) > Can you still reproduce the issue if you try again? I can. Not when syncing, but when trying to do a dnf install. I tried to dnf install gitk and got the following message: [MIRROR] tk-6.8.10-8.el9.x86_64.rpm: Interrupted by header callback: Server reports Content-Length: 1704590 but expected size is: 1704086
The log line says it's the tk package not the gitk package, but gitk pulls in "tk" as a dependency so that still makes sense. Could you download the repomd.xml and $$$-primary.xml metadata your Satellite is distributing for that repo and attach it? Also which Satellite release are you on presently, 6.10.4?
(In reply to Daniel Alley from comment #24) > The log line says it's the tk package not the gitk package, but gitk pulls > in "tk" as a dependency so that still makes sense. > > Could you download the repomd.xml and $$$-primary.xml metadata your > Satellite is distributing for that repo and attach it? > > Also which Satellite release are you on presently, 6.10.4? Actually haven't updated in a while so it's Satellite 6.10.1. Not sure the best way to capture repomd.xml and $$$-primary.xml
@thattguy24601 Have you tried with a newer version and/or the official RHEL 9 release?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days