Bug 1343667

Summary:	Unable to provision more than 6 hosts in parralel
Product:	Red Hat Satellite	Reporter:	Karim Boumedhel <kboumedh>
Component:	Foreman Proxy	Assignee:	Dmitri Dolguikh <ddolguik>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.1.3	CC:	bbuckingham, bkearney, ealcaniz, lzap, pmoravec, satellite6-bugs
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
URL:	http://projects.theforeman.org/issues/12319
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-20 10:10:57 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 Karim Boumedhel 2016-06-07 15:55:29 UTC

Description of problem:
launch provisioning of more than 6 concurrent hosts and watch capsule process dies

Version-Release number of selected component (if applicable):
foreman-proxy-1.7.2.6-1.el7sat.noarch

How reproducible:
launch provisioning of more than 6 concurrent hosts and watch capsule process dies

Steps to Reproduce:
1.launch provisioning of more than 6 concurrent hosts 
2.wait
3.cry

Actual results:
provisioning of more than 6 concurrent hosts and watch capsule process dies

Expected results:
provisioning of more than 6 concurrent hosts and watch capsule process should work

Additional info:
we believe the fix is to fine tune the passenger.conf of the capsule so that the parameter PassengerMaxPoolSize is set to an higher value.
PassengerMaxPoolSize 30 does the trick but other tweaks should be applied as stated in https://access.redhat.com/sites/default/files/attachments/sat6-perfbrief-v1.0.pdf

Comment 2 Edu Alcaniz 2016-06-16 06:35:57 UTC

Customer get a problem in the production environment. Could we get an update.

Comment 3 Pavel Moravec 2016-06-16 10:41:16 UTC

I think [1] is the relevant upstream bug / dup of [2]. This has been fixed in 6.1.9 (or some prior z-stream version). Definitely I see the patch applied to foreman-proxy-1.7.2.8-1.el7sat.noarch distributed with 6.1.9.

Checking the attached support cases, foreman-proxy version is 1.7.2.6-1 where the fix is not present.

Lukas, could you please confirm if the [1] applies for any type of rendering?

[1] http://projects.theforeman.org/issues/12319
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1275647

Comment 4 Lukas Zapletal 2016-06-16 11:49:20 UTC

That is definitely relevant. Yes, it applies to any template, I just used iPXE because it was easy to test with. The bug that has been fixed in 6.1.9. Please:

1) Check that customer upgraded to 6.1.9.
2) Try the reproducer shell script from http://projects.theforeman.org/issues/12319 if it breaks the proxy process

Comment 5 Bryan Kearney 2016-06-16 12:16:06 UTC

Upstream bug assigned to ddolguik

Comment 6 Bryan Kearney 2016-06-16 12:16:09 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/12319 has been closed

Comment 7 Brad Buckingham 2016-06-16 12:25:27 UTC

Hi Edu, please confirm if the customer has updated to 6.1.9 and if it has resolved the issue.  Thanks!

Comment 10 Edu Alcaniz 2016-06-20 09:32:38 UTC

Customer upgrade to 6.1.9 and it seems that it worked. Thanks so much.

[root@server01:~]# rpm -qa | grep foreman-proxy
...
foreman-proxy-1.7.2.8-1.el7sat.noarch

Comment 11 Pavel Moravec 2016-06-20 10:10:57 UTC

(In reply to Edu Alcaniz from comment #10)
> Customer upgrade to 6.1.9 and it seems that it worked. Thanks so much.
> 
> [root@server01:~]# rpm -qa | grep foreman-proxy
> ...
> foreman-proxy-1.7.2.8-1.el7sat.noarch

Thanks for confirming it, closing as DUP of bz1275647.

*** This bug has been marked as a duplicate of bug 1275647 ***