Bug 1661410

Summary: controller-manager pod turn to CrashLoopBackOff after deployed ASB or TSB by operator
Product: OpenShift Container Platform Reporter: Zhang Cheng <chezhang>
Component: Service CatalogAssignee: Dan Geoffroy <dageoffr>
Status: CLOSED ERRATA QA Contact: Zhang Cheng <chezhang>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.0CC: jfan, jiazha, zitang
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:41:27 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:

Comment 1 Jay Boyd 2019-01-16 14:27:49 UTC 
fixed by https://github.com/operator-framework/operator-lifecycle-manager/pull/649
Comment 3 Zihan Tang 2019-01-25 06:07:31 UTC 
Verified.
version: v4.0.0-v0.1.38+abebed4-4-dirty;Upstream:v0.1.38
After increase cpu and memory size, controller pod becomes more stable.

$ oc get deployment apiserver -o yaml
....
        resources:
          limits:
            cpu: 100m
            memory: 140Mi
          requests:
            cpu: 100m
            memory: 40Mi
....       
      resources:
          limits:
            cpu: 100m
            memory: 150Mi
          requests:
            cpu: 100m
            memory: 50Mi
Comment 7 errata-xmlrpc 2019-06-04 10:41:27 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, 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-2019:0758