Bug 1883694

Summary: Search pod collector crashes with Runtime: goroutine stack exceeds 1000000000-byte limit fatal error: stack overflow in ACM
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Jared Deubel <jdeubel>
Component: Search / AnalyticsAssignee: shvarugh
Status: CLOSED ERRATA QA Contact: Song Lai <slai>
Severity: medium Docs Contact: Mikela Dockery <mdockery>
Priority: high    
Version: rhacm-2.0CC: amcnamar, jpadilla
Target Milestone: ---Flags: amcnamar: rhacm-2.0.z+
Target Release: rhacm-2.0.4   
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: 2020-10-06 17:58:24 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 Jared Deubel 2020-09-29 21:33:10 UTC
Description of problem:

One of the pod in ACM deployment Crashes frequently with the 

=================================================
runtime: goroutine stack exceeds 1000000000-byte limit
fatal error: stack overflow
=================================================

The pod name is search-prod-cb232-search-collector-fd7c6498f-tmkhj and the deployment managing this pod is search-prod-cb232-search-collector.

It crashed with in 10-15 mins for the restart.


Version-Release number of selected component (if applicable):
2.0.3

Comment 2 Jorge Padilla 2020-09-29 21:57:24 UTC
Looks like a circular ownerReference is creating an infinite recursion loop in the logic that creates relationships. We are working on the fix.

Comment 8 errata-xmlrpc 2020-10-06 17:58:24 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 (RHACM 2.0.3 search-collector hotfix), 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-2020:4192