Problem: The Proxy Status sync doest update, it get stuck
Expected outcome: Proxy sync job and actual status task expected to sync
Foreman and Proxy versions: Foreman 3.17.0, Proxy 3.17.0, Katello 4.19.0
Foreman and Proxy plugin versions: 3.17.0
Distribution and version: RHEL 9.6
Other relevant data:
After performing the upgrade to foreman 3.17.0 and katello 4.19.0, I have observed that the proxies status are getting stuck at less than 50%, but the sync task is completing correctly. I am guessing this is some sort of bug in the sync process. Is there any way tot roubleshot this o a workaround to get the sync status sync with the actual task status. See reference below
I see this as a UI-only issue here with status saying “Synchronized” on Capsule page while the sync task is in progress. That shouldn’t cause any issues with your content workflows as long as the sync itself completes successfully.
Can you make sure all Capsule sync tasks are succeeding and running?
The task progress bar provides a more accurate representation of the sync status compared to the “Smart proxy is synchronized” text. If you see the progress bar, that means an active sync is currently running on the capsule.
Hi @sajha , thank you for the reply. Yes the synchronization is happening without issues, but is now to have the status bar working. I always keep an eye on that status bar, not urgent but it would be nice to get this working in the next lifecycle patch/release. Thoughts ?
Hi @sajha , The challenge remains the status bar gets stuck and never completes….but the task itself does complete without issues, I suspect this is bug somewhere that need further review/investigation. PLease advise on direction.
My hunch is there is a stuck granular sync task aka CV or Repo sync triggered task or a reclaim space task running against the capsule. The UI is showing the data it gets from the API at the endpoint server_url/katello/api/v2/capsules/"capsule_id"/content/sync which has this key: active_sync_tasks which shows up as the progress bar. You could try looking at what you see in that and get to the task it is pointing to if that helps.