Bug 1781671
| Summary: | While using concurrency_level in remote execution, job progress in WebUI is not being updated properly | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Barbora Vassova <bvassova> | |
| Component: | Remote Execution | Assignee: | Adam Ruzicka <aruzicka> | |
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 6.6.0 | CC: | aruzicka, eero.torri, fperalta, hakon.gislason, hyu, inecas, janarula, kkinge, kkohli, mkalyat, mmccune, pierre-yves.goubet, pmoravec, satellite6-bugs, smutkule, wclark | |
| Target Milestone: | 6.8.0 | Keywords: | Triaged | |
| Target Release: | Unused | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1832580 1851137 (view as bug list) | Environment: | ||
| Last Closed: | 2020-10-27 12:59:35 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Attachments: | ||||
|
Description
Barbora Vassova
2019-12-10 11:30:25 UTC
Connecting upstream issue to this BZ This won't probably be an easy fix. Until we have a fix ready, the following workaround can be used: Go to Settings > Foreman Tasks > set 'foreman_tasks_proxy_batch_trigger' to false. Please note this can lead to degraded performance of remote execution in case you have *lots* of hosts. Upstream bug assigned to aruzicka Upstream bug assigned to aruzicka Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28095 has been resolved. This also needs https://projects.theforeman.org/issues/28616. Moving back to ASSIGNED until the other patch is merged. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28616 has been resolved. (In reply to Adam Ruzicka from comment #5) > This won't probably be an easy fix. Until we have a fix ready, the following > workaround can be used: > > Go to Settings > Foreman Tasks > set 'foreman_tasks_proxy_batch_trigger' to > false. Please note this can lead to degraded performance of remote execution > in case you have *lots* of hosts. I tried this workaround but it is also broken. The jobs failed because ansible jobs are treated as a remote execution jobs. It is because the old API which is using the hardcoded "proxy_action_name" (ForemanRemoteExecutionCore::Actions::RunScript) is used to trigger the remote tasks. The patch for this bugzilla also fixed this issue. Created attachment 1676643 [details]
hotfixed tfm-rubygem-foreman-tasks RPM for Satellite 6.6.2
Created attachment 1676644 [details]
hotfixed tfm-rubygem-foreman_remote_execution RPM for Satellite 6.6.2
A hotfix for this issue is available for Satellite 6.6.2. INSTALLATION INSTRUCTIONS: 1. Make a complete backup or snapshot of Satellite server 2. Download the attached hotfix RPMs from this BZ and copy them to Satellite server 3. # foreman-maintain packages unlock 4. # yum install ./tfm-rubygem-foreman_remote_execution-1.8.0.4-2.HOTFIXRHBZ1781671.el7sat.noarch.rpm ./tfm-rubygem-foreman-tasks-0.15.11.1-2.HOTFIXRHBZ1781671.el7sat.noarch.rpm 5. # foreman-maintain packages lock 6. # systemctl restart dynflowd httpd Created attachment 1679406 [details]
UPDATED tfm-rubygem-foreman_remote_execution hotfix RPM
There was an issue with the previous version of this RPM. Please use the newly uploaded version.
Verified on Sat 6.8 snap 5, the concurrency level setting is accepted with foreman_tasks_proxy_batch_trigger true Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Satellite 6.8 release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4366 The hotfix for 6.6.2 in this bugzilla is also applicable to 6.6.3 if needed. |