Bug 1941563 - High RAM usage on machine api termination node system oom
Summary: High RAM usage on machine api termination node system oom
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.6.z
Assignee: Joel Speed
QA Contact: Milind Yadav
URL:
Whiteboard:
Depends On: 1935636
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-22 11:19 UTC by OpenShift BugZilla Robot
Modified: 2021-04-20 19:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: HTTP requests were not being closed once they were no longer needed Consequence: In Go, this leaks go routines which over time, increases memory usage Fix: Ensure that the HTTP request is always closed when it is no longer needed Result: Memory usage is now stable in termination handlers
Clone Of:
Environment:
Last Closed: 2021-04-20 19:27:22 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-api-provider-aws pull 395 0 None open [release-4.6] Bug 1941563: Ensure response body is closed when we are finished with the request 2021-03-22 17:13:06 UTC
Github openshift cluster-api-provider-azure pull 210 0 None open [release-4.6] Bug 1941563: Ensure response body is closed when we are finished with the request 2021-03-22 17:13:43 UTC
Github openshift cluster-api-provider-gcp pull 154 0 None open [release-4.6] Bug 1941563: Ensure response body is closed when we are finished with the request 2021-03-22 17:14:21 UTC
Red Hat Product Errata RHBA-2021:1153 0 None None None 2021-04-20 19:27:39 UTC

Comment 2 Milind Yadav 2021-03-29 04:38:53 UTC 
Validated details below :



[miyadav@miyadav aws]$ kubectl top pod 
NAME                                           CPU(cores)   MEMORY(bytes)   
cluster-autoscaler-operator-5464c4b7b7-jzjbm   0m           32Mi            
machine-api-controllers-84464f8875-qcnxc       0m           110Mi           
machine-api-operator-69c9bcf67c-lvrr6          0m           38Mi            
machine-api-termination-handler-9dm6q          0m           14Mi            
[miyadav@miyadav aws]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.6.0-0.nightly-2021-03-27-052141   True        False         37m     Cluster version is 4.6.0-0.nightly-2021-03-27-052141
[miyadav@miyadav aws]$ 


Additional info :

Spinned a spot instance in AWS  to get the machine-handler pod up ...
Moved to verified
Comment 8 errata-xmlrpc 2021-04-20 19:27:22 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 (OpenShift Container Platform 4.6.25 bug fix 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/RHBA-2021:1153
Note You need to log in before you can comment on or make changes to this bug.