Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
If user chooses a very small task batch size (e.g. 1 or 2) it may happen that some RunHostJob(s) get stuck in running/pending (suspended) status forever.
One has to then clean/cancel the tasks to get rid of them:
# sudo su - postgres -c "psql -d foreman -c 'select label,count(label),state,result from foreman_tasks_tasks where state <> '\''stopped'\'' group by label,state,result ORDER BY label;'"
label | count | state | result
------------------------------------------------------+-------+-----------+---------
Actions::RemoteExecution::RunHostJob | 2 | running | pending
Actions::RemoteExecution::RunHostsJob | 1 | running | pending
Version-Release number of selected component (if applicable):
Satellite 6.12
How reproducible:
Sort of (not 100% deterministic)
Steps to Reproduce:
1. Set batch size to 1:
- Administer -> Settings -> Tasks -> Capsule tasks batch size -> 1
- Administer -> Settings -> Ansible -> Capsule tasks batch size for Ansible -> 1
2. Have a set of hosts (I used 13) and schedule a recurring job for them:
- Monitor -> Jobs -> Run Job -> Ansible Playbook; Ansible Roles - Ansible Default
- Custom cron so the job runs every minute (*/1 * * * *)
- Repeat N times: 10
Actual results:
- Some job iterations result in forever running RunHostJob(s) tasks.
- Inspecting the job task shows the following error:
~~~
Error loading data from Capsule: RestClient::NotFound - 404 Not Found
~~~
- For more clarity see attached screenshots.
Expected results:
- The 404 errors do not occur.
- Jobs are not stuck in running/pending state forever.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: If user chooses a very small task batch size (e.g. 1 or 2) it may happen that some RunHostJob(s) get stuck in running/pending (suspended) status forever. One has to then clean/cancel the tasks to get rid of them: # sudo su - postgres -c "psql -d foreman -c 'select label,count(label),state,result from foreman_tasks_tasks where state <> '\''stopped'\'' group by label,state,result ORDER BY label;'" label | count | state | result ------------------------------------------------------+-------+-----------+--------- Actions::RemoteExecution::RunHostJob | 2 | running | pending Actions::RemoteExecution::RunHostsJob | 1 | running | pending Version-Release number of selected component (if applicable): Satellite 6.12 How reproducible: Sort of (not 100% deterministic) Steps to Reproduce: 1. Set batch size to 1: - Administer -> Settings -> Tasks -> Capsule tasks batch size -> 1 - Administer -> Settings -> Ansible -> Capsule tasks batch size for Ansible -> 1 2. Have a set of hosts (I used 13) and schedule a recurring job for them: - Monitor -> Jobs -> Run Job -> Ansible Playbook; Ansible Roles - Ansible Default - Custom cron so the job runs every minute (*/1 * * * *) - Repeat N times: 10 Actual results: - Some job iterations result in forever running RunHostJob(s) tasks. - Inspecting the job task shows the following error: ~~~ Error loading data from Capsule: RestClient::NotFound - 404 Not Found ~~~ - For more clarity see attached screenshots. Expected results: - The 404 errors do not occur. - Jobs are not stuck in running/pending state forever.