Bug 1645465 - Service Catalog establishes a new connection for every request and never closes them.
Summary: Service Catalog establishes a new connection for every request and never clos...
Keywords:
Status: CLOSED DUPLICATE of bug 1641791
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Catalog
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.10.z
Assignee: Jay Boyd
QA Contact: Zhang Cheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-02 09:53 UTC by Jian Zhang
Modified: 2018-11-02 13:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-02 13:51:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jian Zhang 2018-11-02 09:53:18 UTC
Description of problem:
This is a copy from bug 1628235 for the OCP 3.10.

Version-Release number of selected component (if applicable):
v3.10.68;Upstream:v0.1.19

How reproducible:
alway

Steps to Reproduce:
1. Write down the connection count between the ansible-service-broker and service-catalog.
You can access the node with the ansible-service-broker running on.
Get its pid, and write down the connection counts. Like below:
#ps -elf | grep broker
#nsenter -t ${BROKER_PID} --net netstat -n | grep ESTABLISHED | wc

2. Do some privision/deprovision operations. And, do some sync operations between the ansible-service-broker and service-catalog, such as:
#svcat sync broker ansible-service-broker

3. Check the connection counts again.
#nsenter -t ${BROKER_PID} --net netstat -n | grep ESTABLISHED | wc

Actual results:
The count is increased.

Expected results:
The count should not increase.

Additional info:
The fixed PR is: https://github.com/openshift/service-catalog/pull/28

Comment 1 Jay Boyd 2018-11-02 13:51:33 UTC
Hi Jian.  There's some confusion on how I tracked the fix for this issue.  I'm going to mark this a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1641791  as this is the same issue.

For reference, the "sockets are never closed" issue is tracked by the following BZs:

3.9: https://bugzilla.redhat.com/show_bug.cgi?id=1638726
3.10: https://bugzilla.redhat.com/show_bug.cgi?id=1641791
3.11: https://bugzilla.redhat.com/show_bug.cgi?id=1641796

Sorry for the confusion.  Please let me know if this doesn't make sense or if you would prefer to track this in another manner.

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


Note You need to log in before you can comment on or make changes to this bug.