yes, smart proxies didn’t sync the packages from the master once I published a new version of the CV. So either change the db there too, update the pulp package to fixed version or change the python scripts as Macley suggested manually.
any of you guys having issues with syncing? with update to 4.17 i get random sync issues, sometimes invidiual repos fail with pulp error, sometimes the whole sync plan fails to finish and has to be killed with rake console.
I see no pattern, random repositorys, somtimes it does not happen at all. But right now, i have to intervene atleast 1-2 times a week to get sync working again.
Is it possible that your system is resource-constrained due to the (resolved) issue from Slow generate applicability ? That issue can leave the server spending all its time running slow postgres queries, which could hurt sync performance.
This comment is potentially related to Smart proxy sync throws Katello::Errors::Pulp3Error - #3 by iballou
Forget to give some feedback, the issue disappeared few days later, i dont think i got any package updates for foreman/katello at that time, the issues just disappeared.
1 Like
Thanks for the feedback. If you get sync failures in the future, let us know if you see any core dumps in the system logs from Pulp.