Bug 1420397

Summary:	Expose the foreman-tasks pool size via config/installer
Product:	Red Hat Satellite	Reporter:	Ivan Necas <inecas>
Component:	Tasks Plugin	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Perry Gagne <pgagne>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.2.0	CC:	aruzicka, bkearney, egolov, inecas, jcallaha, pgagne
Target Milestone:	6.4.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-dynflow-1.0.5.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 19:05:40 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:

Description Ivan Necas 2017-02-08 14:48:47 UTC

Currently, we use a pool of 5 workers in the foreman-tasks to handle the incoming requests. At large scale, this might not be enough. For start, we should be
at least able to set the number of works via config file/installer

As a workaround, one would need to edit `pool_size` in initialize method of

  /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-*/lib/foreman_tasks/dynflow/configuration.rb

and after changing the size, restart the foreman-tasks service

Comment 1 Ivan Necas 2017-02-08 14:49:19 UTC

Created redmine issue http://projects.theforeman.org/issues/18422 from this bug

Comment 3 Satellite Program 2017-09-21 14:08:50 UTC

Upstream bug assigned to aruzicka

Comment 4 Satellite Program 2017-09-21 14:08:53 UTC

Upstream bug assigned to aruzicka

Comment 5 Satellite Program 2017-10-10 00:10:38 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18422 has been resolved.

Comment 14 Bryan Kearney 2018-10-16 19:05:40 UTC

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, 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-2018:2927