Bug 1912066

Summary:	The ansible type operator's manager container is not stable when managing the CR
Product:	OpenShift Container Platform	Reporter:	Fan Jia <jfan>
Component:	Operator SDK	Assignee:	Jesus M. Rodriguez <jesusr>
Status:	CLOSED ERRATA	QA Contact:	Fan Jia <jfan>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.7	CC:	aos-bugs, chezhang, chuo, jesusr, jiazha
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Cause: The operator-sdk v1.3.0 changed the location of the scaffolded liveness proves for scaffolded projects. If you use operator-sdk v1.3.0 scaffolded project with a v1.2.0 ansible/helm operator base image, the paths do not match causing the CrashLoopBackOff. Consequence: Potential for CrashLoopBackOff in the operator pods Workaround (if any): 1. Use a corresponding v1.3.0 or later ansible/helm operator base image 2. Update the scaffolded liveness prove check paths to match the v1.2.0 paths used by the older base images Result: If you use matching base images there is no problem. Or if you update the new projects liveness prove check paths to match the ones in the v1.2.0 paths things will work as well.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:49:31 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 Jesus M. Rodriguez 2021-01-07 20:13:41 UTC

Please test with:
* binary extracted from the downstream image: registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-sdk:v4.7.0-202101071845.p0 (or wherever you typically get test images)
* the v1.3.0 released binary: https://github.com/operator-framework/operator-sdk/releases/tag/v1.3.0

The problem you are running into is that the code in master will scaffold the liveness probes using the `healthz` url path. But it uses the `quay.io/operator-framework/ansible-operator:v1.3.0` base image which does NOT have that path. 

So this version,  "v1.3.0-5-g50fcdb8", of the operator-sdk won't work until it is been released with an updated ansible-operator base image.  Please retest with the versions listed above.

Comment 5 errata-xmlrpc 2021-02-24 15:49:31 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