Rhel9 repo sync failed, error message is: failed: '404, message='Not Found' for some packages

Support
#1

Hello

I tried to sync our internal RHEL9 repo to the pulp3 server run by docker-composer

"core", "version": "3.49.4", 
"rpm": "3.25.2"

The sync policy is mirror_content_only. Remote policy is 'immediate

sync task failed with the error:

404, message='Not Found', url=URL('http://xx.xx.xxr/mrepo/rhel9-x86_64/depot-appstream/Packages/a/aspnetcore-targeting-pack-6.0-6.0.3-1.el9_0.x86_64.rpm')

This package doesn’t exist on remote rhel repo.

I also open an issue here failed: '404, message='Not Found' for some packages while doing RHEL9 repo sync · Issue #3507 · pulp/pulp_rpm · GitHub ,

Is it more a problem on our rhel remote repo? This server is not managed by me. What should I do?

Thanks in advance

#2

I looked at rhel9.3-appstream, and did a sync into my pulp-instance just to be sure, and aspnetcore-targeting-pack-6.0-6.0.3-1.el9_0.x86_64.rpm is definitely available on CDN. It sounds like your internal rhel9 repo’s metadata says “I have this package available”, in primary.xml.gz - but it’s actually not in that repo, for whatever reason. So pulp syncs, gets the list of packages from primary, fails to find one, and says “this repo Has A Problem” and aborts. There’s not much we can do from the pulp-side - sounds like whoever owns that repo, needs to re-mrepo it to fix it, unless you can point your Pulp instance to https://cdn.redhat.com/content/dist/rhel9/9.3/x86_64/appstream/os/ directly, of course…

#3

@ggainey thank you very much for the test. I will check on our internal server side. The person in charge of it will be back next week.

1 Like
#4

The problem on our internal RHEL repo server side is fixed. pulp sync works well now.

1 Like
#5

Outstanding - thanks for coming back and letting us know!