Bug 1748807

Summary:	[Baremtal and Openstack] API LB supports maximum 2k concurrent connections
Product:	OpenShift Container Platform	Reporter:	Yossi Boaron <yboaron>
Component:	Machine Config Operator	Assignee:	Yossi Boaron <yboaron>
Status:	CLOSED ERRATA	QA Contact:	Michael Nguyen <mnguyen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.0
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:40:12 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 Yossi Boaron 2019-09-04 08:22:49 UTC

Description of problem:
API LB uses the default value of maximum concurrent connections which is 2K, this value should be increased. 

Version-Release number of selected component (if applicable):
42.80.20190827.1

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Antonio Murdaca 2019-09-04 09:22:46 UTC

(In reply to Yossi Boaron from comment #0)
> Description of problem:
> API LB uses the default value of maximum concurrent connections which is 2K,
> this value should be increased. 
> 
> Version-Release number of selected component (if applicable):
> 42.80.20190827.1
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

Thank you for this bug but you could have at the very least provided more information on how the MCO is in charge of this? steps to reproduce perhaps? I don't have any clue about how a team is supposed to tackle a bug reported like this. It's literally missing everything, and we have a template for a reason for reporter to fill.

Comment 2 Antonio Murdaca 2019-09-04 09:24:33 UTC

I cannot see how, from the very few lines of this bug, the MCO could be in charge of the API LB (assuming that stands for API LoadBalancer)

Comment 3 Antonio Murdaca 2019-09-04 09:26:29 UTC

Ok, I"m now seeing the PR in MCO

Comment 6 errata-xmlrpc 2019-10-16 06:40:12 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/RHBA-2019:2922