Bug 1416018

Summary: rlWaitForSocket --close - performance problems after recent change
Product: [Fedora] Fedora Reporter: Stanislav Zidek <szidek>
Component: beakerlibAssignee: Dalibor Pospíšil <dapospis>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: rawhideCC: azelinka, dapospis, fsumsal, hkario, jprokes, mkyral, muller
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-24 11:15:29 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 Stanislav Zidek 2017-01-24 11:14:08 UTC 
Description of problem:
After fixing bz1388422, new behaviour brings serious performance penalty because of waiting in close_wait state. We are experiencing great difficulties e.g. in our scenario of testing tls libraries' interoperability.

I think the old behaviour (ignoring sockets with TIME_WAIT) should remain as default and users who really want to wait for this should state it explicitly, e.g. with extra argument.

Version-Release number of selected component (if applicable):
beakerlib-1.12-1

How reproducible:
always

Steps to Reproduce:
1. openssl s_server -key .. -cert .. &
2. (echo Q; sleep 3) |openssl s_client -CAfile ..
3. killall openssl
4. netstat -atn |grep 4433
5. rlWaitForSocket --close 4433

Actual results:
...
tcp        0      0 ::1:35176                   ::1:4433                    TIME_WAIT   
... waits for almost a minute

Expected results:
wait ends almost instantly
Comment 1 Dalibor Pospíšil 2017-01-24 11:15:29 UTC 

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