@senetm which download policy and which mirroring policy are you using for your related repository? It’s possible that the upstream repository no longer has those packages, so if you’re using on-demand, Pulp may be trying to download them but is unable.
I would recommend using the Immediate download policy with the Additive mirroring policy unless you’re certain that the repository does keep all older versions of packages.
Just in case I’m not on the right track, @quba42 do you think the issue might be something else?
Hi thanks for your answer. I am using On Demand and Content Only.
I have different environments one is promoted to new content view and the other to older one. And after some weeks the promotion starts again and so on. In the first test environment are always the newest packages and in the second older packages which were tested before in the test environment. Only productive environment is synced to other smart proxies.
What would be the right policy for that case?
Can’t be 100% sure without knowing what upstream repo is being synced with what options, but this sure looks and sounds like the problem is Download Policy: On Demand plus changing packages in the upstream remote repo. If so, then switching to Download Policy: Immediate will fix the issue (at least for all new content view versions created after the download policy was switched and everything re-synced).
As to Mirroring Policy: Content Only vs Additive depends on whether you want to keep old packages in new content view versions indefinitely. Even with Content Only things that make it into some version won’t disappear from that version, so what you see is what you get. @iballou I am unclear on when one really needs Additive…
One more side note: Even if you use Download Policy: Immediate on your server, there is then no reason not to use Download Policy: On Demand (or even Streamed) for your smart porxy syncs. Since the smart proxy syncs from the server, and the server will keep everything that should always be safe.
