Bug 1556773

Summary:	Deprecated env option DROP_SYN_DURING_RESTART for router
Product:	OpenShift Container Platform	Reporter:	zhaozhanqi <zzhao>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	router	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	low	CC:	aos-bugs, rpenta
Version:	3.9.0
Target Milestone:	---
Target Release:	3.9.z
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:	2018-08-29 14:42:31 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 zhaozhanqi 2018-03-15 08:54:21 UTC

Description of problem:
since from 3.9 the router is using haproxy 1.8 which already resolved the seamless reload. more details https://www.haproxy.com/blog/truly-seamless-reloads-with-haproxy-no-more-hacks/
So if related env DROP_SYN_DURING_RESTART and reldated codes in reload-haproxy can be deprecated?

Version-Release number of selected component (if applicable):
oc v3.9.9
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO


How reproducible:


Steps to Reproduce:
1. As Description
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ravi Sankar 2018-08-02 17:34:13 UTC

Fixed by https://github.com/openshift/origin/pull/19315

Comment 2 zhaozhanqi 2018-08-13 08:38:22 UTC

I saw the fixed PR only merged to 3.10. please correct me if I'm wrong.
since this bug was reported to 3.9, can we backport it to 3.9 as well. thanks.

Comment 3 Ravi Sankar 2018-08-14 18:44:19 UTC

3.9 backport pr: https://github.com/openshift/ose/pull/1390

Comment 5 zhaozhanqi 2018-08-27 03:23:06 UTC

verified this bug on v3.9.41, the reldated codes in reload-haproxy has been deprecated.

Comment 7 errata-xmlrpc 2018-08-29 14:42:31 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-2018:2549