Bug 1902091

Summary:	`cluster-image-registry-operator` pod leaves connections open when fails connecting S3 storage
Product:	OpenShift Container Platform	Reporter:	Anshul Verma <ansverma>
Component:	Image Registry	Assignee:	Ricardo Maraschini <rmarasch>
Status:	CLOSED ERRATA	QA Contact:	Wenjing Zheng <wzheng>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5	CC:	aos-bugs, obulatov, rmarasch
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:36:28 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:
Bug Depends On:
Bug Blocks:	1959563

Description Anshul Verma 2020-11-26 21:02:56 UTC

Description of problem:

The cluster-image-registry-operator, when a request to the associated S3 storage fails with any reason, it leaves the connection created for that request open.
This blocks a port. When this keeps happening, no more ports gets available for new connections and it gives the following error -
~~~
E1019 06:23:08.149459      90 controller.go:311] unable to sync: unable to sync storage configuration: RequestError: send request failed
caused by: Head https://<s3_storage>: dial tcp <ip_address>:443: connect: cannot assign requested address, requeuing
~~~

Comment 11 Wenjing Zheng 2021-01-12 08:40:58 UTC

Looking at the PR we are only setting some defaults for timeouts, a regression test should be enough to verify this bug.
Verified on 4.7.0-0.nightly-2021-01-10-070949.

Comment 14 errata-xmlrpc 2021-02-24 15:36:28 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633