Scheduled future Remote Jobs stays in Queued state past set time.
Environment
- Red Hat Satellite 6.3.x onwards.
Issue
- Scheduled future Remote Jobs stays in "queued" state even after the set time is passed.
- Scheduled remote jobs never initiate, but if they are executed "now" they will finish successfully.
Resolution
- Restart the foreman-tasks service as it is only responsible for executing remote jobs on the clients registered to Red Hat Satellite. Execute below command on the Red Hat Satellite Command Line:
systemctl restart dynflow-sidekiq@*.service
(for Sat6.7 or older, use systemctl restart foreman-tasks instead)
For more KB articles/solutions related to Red Hat Satellite 6.x Remote Execution Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Remote Execution Issues
Root Cause
There is no set rule or frequency on which should be restarted the service, but the worlds executor should always be set to true and when checked the status it should be valid. Foreman_tasks service is especially responsible for handling remote execution.
To check the status at:
So there is no harm if restarted this service on regular time intervals or see the status on the above URL.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.