Problem: receiving status code 404, that the package is not found when downloading from foreman after upgrade to 3.16
Expected outcome: correctly install package from https://foreman-example/pulp/content/
Foreman and Proxy versions: 3.16.2
Foreman and Proxy plugin versions:
Distribution and version: CentOS Stream 9
Other relevant data:
We have compared repodata from original source and with foreman. We noticed, that the name of package in location url is created from name, version and architecture. The original name of package from upstream repo is changed. We have problem with three repositories (Grafana, Filebeat and MongoDB). We checked the naming of package by installing two new foremans from scrats (3.15 and 3.16).
alloy x86_64 ad764ad8e1401328590286fd9128c1c1e17bf3c8711923d550be99b5bb5af72cYou can see above that the name of package in foreman is named alloy-1.11.3-1.x86_64.rpm, because the architecture is x86_64. But the artifact saved is Packages/a/alloy-1.11.3-1.amd64.rpm. This incosistecy causes problem during download
[MIRROR] alloy-1.11.3-1.x86_64.rpm: Status code: 404 for https://foreman-example/pulp/content/TEST/PROD/CCV_el9_default/custom/Grafana/grafana/Packages/a/alloy-1.11.3-1.x86_64.rpm
It’s a problem of MongoDB, Grafana,Filebeat and maybe some else.
I’ve tried different sync method, trying delete all repository and clean all date of grafana and resync created new one. I also tried new upgrade of foreman. Tried katello:correct_repositories and also metadata regenerate. Nothing helped to me.
Is something wrong in our foreman? Can it be somehow repaired?
Thank you very much in advance.
Best regards,
Ondrej