Problem:
Unable to kill the sync process. Tried multiple commands still the sync seems to be struck
rb(main):002:0> ForemanTasks::Task.where(:state => ‘running’).pluck(:id, :label)
=>
[[“bcd8b33a-0576-43ef-81c6-4776f1ed7113”, “Actions::Katello::SyncPlan::Run”],
[“bf3373df-6108-4959-bfaf-937155c6f0c3”, “Actions::Katello::Repository::Sync”],
[“9db23b9f-cdc2-4b5c-aa2c-ed98c69242ec”, “Actions::Katello::Repository::Sync”]]
irb(main):003:0>
Due to which unable to re-run the sync and it says no content added
Expected outcome:
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
Distribution and version:
Other relevant data:
Hi @toypatrick ,
Did you try cancelling the task from the foreman tasks page for it?
Can you tell in the Dynflow console which part was hanging? Was it the Pulp task?
If it’s really stuck - did you try the force unlock option on it? Worst case you could delete the repository and recreate it.
And no resource limits are being reached (CPU/RAM/Storage)? If all workers are busy it could hang.
Thanks for the quick response,
- I had force canceled the tasks and also executed
- ForemanTasks::Task.find(“ForemanTasks::Task.find(“1a2b3c4d-5e6f-7890-abcd-ef1234567890”).cancel”).cancel
- I had restarted the server stil the same
- Could you let me know how to check – Dynflow console which part was hanging? Was it the Pulp task?
- The disk utilization is also at 70%
1 Like
Hi @toypatrick ,
Apologies for the delay. I’m guessing you might be past this issue now, but for the future, on the Foreman Tasks page for the task, if you click the “Dynflow Console” button, you’ll be able to look at the full execution plan for the problematic task. On the “Running Steps” tab, you’ll see which actions are being waited on. For example, perhaps in this case one of the Pulp actions was taking a long time. In one of the expandable rows within the Running Steps tab, you can view output from tasks. For example, in the sync task, one of the rows should have a Pulp task in the output.
